-
Couldn't load subscription status.
- Fork 13.9k
ci: Increase rust.debuginfo-level-tests to 2 in x86_64-gnu-debug job
#146394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Can someone do |
|
@bors try jobs=x86_64-gnu-debug |
This comment has been minimized.
This comment has been minimized.
ci: Increase `rust.debuginfo-level-tests` to `2` in **x86_64-gnu-debug** try-job: x86_64-gnu-debug
|
@bors2 delegate=try |
|
✌️ @Enselic, you can now perform try builds on this pull request! You can now post |
| --enable-debug \ | ||
| --enable-lld \ | ||
| --set rust.debuginfo-level-tests=1 \ | ||
| --set rust.debuginfo-level-tests=2 \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remark: (not against this change) I seem to recall that there are meaningful differences between debuginfo level 1 and 2 (in that some bugs are present only at specific debuginfo levels)...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that testing both level 1 and level 2 give the most test coverage, but I also suspect that only level 2 will be sufficient in practice.
If we end up getting a lot of debuginfo level 1-specific problems I think we should look into testing both levels in CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, let's see if there are a few specific-to-1 problems.
This comment has been minimized.
This comment has been minimized.
|
💔 Test for 3e9ca87 failed: CI. Failed jobs:
|
a5939da to
e910daf
Compare
This comment has been minimized.
This comment has been minimized.
…` job Simply to increase the scope of the testing. Force debuginfo=0 for a handful of tests so that we can have CI prevent regressing on more tests.
e910daf to
c7c2fdd
Compare
rust.debuginfo-level-tests to 2 in **x86_64-gnu-debug**rust.debuginfo-level-tests to 2 in x86_64-gnu-debug job
|
@bors2 try jobs=x86_64-gnu-debug |
This comment has been minimized.
This comment has been minimized.
ci: Increase `rust.debuginfo-level-tests` to `2` in `x86_64-gnu-debug` job try-job: x86_64-gnu-debug
|
Try job passed so this is ready for review. I added FIXME to four tests. If we wait with increasing debuginfo level in CI, new tests will probably introduces more failures and existing tests will regress, so I think it makes sense to add FIXMEs. @rustbot ready |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, leaving FIXMEs seem fine.
|
r? jieyouxu @bors r+ rollup=never |
|
☀️ Test successful - checks-actions |
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 9642c0e (parent) -> 064cc81 (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 064cc81354a940e297a1be4dfa9e26759c8431be --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 (064cc81): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (secondary 2.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 2.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 467.368s -> 468.794s (0.31%) |
Simply to increase the scope of the testing.
Part of #61117.
cc #145967 and #146025 which prepared for this. And #144499 that set to level to
1try-job: x86_64-gnu-debug