-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Update Cargo.lock to use the latest compiler_builtins
#57435
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Update Cargo.lock to use the latest compiler_builtins
#57435
Conversation
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Is there any particular reason why we're not bumping the version in the various Line 14 in 7ad470c
|
📌 Commit ef1882c58b448a004a1232c90e924b4813caa3c8 has been approved by |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
☔ The latest upstream changes (presumably #56954) made this pull request unmergeable. Please resolve the merge conflicts. |
ef1882c
to
a0eef7e
Compare
@alexcrichton this is ready for merging |
@bors: r+ |
📌 Commit a0eef7e5d99d3738542d4a505c67560c0e847c26 has been approved by |
@bors p=7 Adjusting queue order for rollups. |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
a0eef7e
to
14a38b3
Compare
@alexcrichton this is ready for a r+ before another PR knocks it down with a merge conflict again 😄 |
@bors r=alexcrichton p=7 |
📌 Commit 14a38b3 has been approved by |
…chton Update Cargo.lock to use the latest `compiler_builtins` A very tiny PR per the request of @alexcrichton : rust-lang/compiler-builtins#267 (comment) Rewrite of #57414 cc @Lokathor r? @alexcrichton
☀️ Test successful - checks-travis, status-appveyor |
A very tiny PR per the request of @alexcrichton : rust-lang/compiler-builtins#267 (comment)
Rewrite of #57414
cc @Lokathor
r? @alexcrichton