rerun in original typing mode if we meet any opaques in post analysis#158993
rerun in original typing mode if we meet any opaques in post analysis#158993adwinwhite wants to merge 1 commit into
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
rerun in original typing mode if we meet any opaques in post analysis
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (82f26fd): comparison URL. Overall result: ❌ regressions - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -2.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 1.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 488.761s -> 488.757s (-0.00%) |
46cf47b to
b4bc03c
Compare
|
|
|
The job Click to see the possible cause of the failure (guessed by this bot) |
When the rerun condition is
OpaqueInStorageand typing mode isPostAnalysis/Codegen, we do rerun the evaluation in original typing mode.It's strange that we don't do the same when the rerun condition is
OpaqueInStorageOrAnyOpaqueHasInferAsHidden.This fixes an ICE when building
cargowith the next solver.r? @jdonszelmann
cc @lcnr