-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Re-enable M1 runners on GitHub Actions #120509
Conversation
@bors try |
Re-enable M1 runners on GitHub Actions r? `@ghost`
☀️ Try build successful - checks-actions |
10d9abf
to
6bcd502
Compare
r? @jdno |
I'm curious to see if the 7GB RAM might be an issue and what the performance of the runners will be. 😅 @bors r+ rollup=never |
The try build took 2h 59m 24s; will be interesting to see how that compares to the future builds. |
☔ The latest upstream changes (presumably #120543) made this pull request unmergeable. Please resolve the merge conflicts. |
6bcd502
to
c2573c7
Compare
☀️ Test successful - checks-actions |
Finished benchmarking commit (94df917): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
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: 662.079s -> 663.088s (0.15%) |
I wonder if these failures are related to this pr:
|
@matthiaskrgr seems unlikely as |
r? @ghost