Conversation
|
@bors r+ rollup=never p=1 |
|
💔 Test failed - checks-actions |
|
A job failed! Check out the build log: (web) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test failed - checks-actions |
@onur-ozkan any idea why this failed? Is it perhaps overly sensitive to the version number? |
|
Can you confirm that #137066 fixes this? |
check if CI-LLVM is enabled before testing it Blocker for rust-lang#137034
Since that one is now under testing, I'll wait for it to merge and then try again. Thanks for the quick response! |
|
@bors retry |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (e72df78): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
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: 789.619s -> 790.103s (0.06%) |
https://forge.rust-lang.org/release/process.html#bump-the-stable-version-number-friday-the-week-before
r? cuviper