In #101680 (af619eb#diff-f699f7fa1d6499f96d393ebaf6be4031125d026a7b6a18d6ecb8ee4e875fa197R161), I changed the Err(NoSolution) to a bug!(). The issue-42552 test originally covered this case, but seems like that's not the case anymore. Instead, when attempting a try run the hyper-0.14.18 benchmark in rustc-perf failed to build.
This issue is basically a call to minimize that failure and add a test to the test suite so we properly capture that bug path.
To do this, you will need to make a local change like the above, calling bug!() instead of returning Err(NoSolution). Then, you can minimize the hyper-0.14.18 benchmark.
In #101680 (af619eb#diff-f699f7fa1d6499f96d393ebaf6be4031125d026a7b6a18d6ecb8ee4e875fa197R161), I changed the
Err(NoSolution)to abug!(). Theissue-42552test originally covered this case, but seems like that's not the case anymore. Instead, when attempting a try run thehyper-0.14.18benchmark in rustc-perf failed to build.This issue is basically a call to minimize that failure and add a test to the test suite so we properly capture that bug path.
To do this, you will need to make a local change like the above, calling
bug!()instead of returningErr(NoSolution). Then, you can minimize thehyper-0.14.18benchmark.