-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Enable RUST_BACKTRACE=1 on CI #145215
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
Enable RUST_BACKTRACE=1 on CI #145215
Conversation
r? @marcoieni rustbot has assigned @marcoieni. Use |
This comment has been minimized.
This comment has been minimized.
We should really see the backtrace if something in bootstrap fails on CI.
@bors r+ |
☀️ 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 5771665 (parent) -> fce0e74 (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard fce0e74720d199eb7839fdb51af35ac5226da178 --output-dir test-dashboard And 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 (fce0e74): 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)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 465.465s -> 464.993s (-0.10%) |
We should really see the backtrace if something in bootstrap fails on CI. #145011 (comment) doesn't show many details.