Use LowerAvailableDepth::No for normalizes-to goal itself instead of its nested goals#158705
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.
Use `IncreaseDepth::No` for normalizes-to goal itself instead of its nested goals
This comment has been minimized.
This comment has been minimized.
25d5250 to
8c7b929
Compare
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (e3dd511): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -8.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 5.5%, secondary -16.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 485.944s -> 485.308s (-0.13%) |
|
r? lcnr |
| goal: Goal<I, I::Predicate>, | ||
| stalled_on: Option<GoalStalledOn<I>>, | ||
| increase_depth_for_nested: IncreaseDepthForNested, | ||
| increase_depth_for_nested: IncreaseDepth, |
There was a problem hiding this comment.
IncrementDepth and also rename the function argument name maybe 🤔 LowerAvailableDepth?
There was a problem hiding this comment.
Since we track available depth, LowerAvailableDepth sounds good 😄
|
naming nit, otherwise r=me 😁 |
…f its nested goals
8c7b929 to
ed57bc8
Compare
IncreaseDepth::No for normalizes-to goal itself instead of its nested goalsLowerAvailableDepth::No for normalizes-to goal itself instead of its nested goals
|
@bors r=lcnr |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 3659db0 (parent) -> 3c00c96 (this PR) Test differencesShow 3 test diffs3 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 3c00c96d3af4d5b5e101e56cc161a608b21366ee --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (3c00c96): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -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 1.4%, secondary -6.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -27.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (secondary -0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 491.532s -> 491.018s (-0.10%) |
Might fix perf regressions in #157718 (comment)