-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Adjust memchr
pinning and run cargo update
#129624
base: master
Are you sure you want to change the base?
Conversation
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. These commits modify the If this was unintentional then you should revert the changes before this PR is merged. The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging. |
Adjust `memchr` pinning and run `cargo update` try-job: x86_64-pc-windows-gnu
This comment has been minimized.
This comment has been minimized.
@bors try |
Adjust `memchr` pinning and run `cargo update` try-job: x86_64-mingw
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Hm. I assume this comes from |
@nagisa it looks like you maintain https://github.com/rust-lang/stacker, any clue if this is related? |
Sounds plausible enough. There's already a PR that bumps it on stacker side, so you'll be able to check this soon enough. |
Ignore the root Cargo.lock for now becuase stacker's Windows dependency may be problematic [1]. Link: rust-lang#129624 (comment) [1]
Okay, I dropped doing a @bors try |
Adjust `memchr` pinning and run `cargo update` try-job: x86_64-mingw
☀️ Try build successful - checks-actions |
…crum Adjust `memchr` pinning and run `cargo update` try-job: x86_64-mingw
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Maybe changing the lock file affects the cache in some way that makes this error more likely to be hit? It does seem incredibly frequent with this PR. |
Yeah I don’t know why this is so weird, especially after your partial fix. When I’m back at a computer I’ll just try splitting it into a separate PR for each lockfile. That is an interesting datapoint for the Windows CI issue if it seems like caching affects things. |
trying to see if this is still a problem, if so #130151 may eliminate one source of failure. |
@bors retry |
…crum Adjust `memchr` pinning and run `cargo update` try-job: x86_64-mingw
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Sorry for using this PR as a kind of canary but I'd like to try just one more time: @bors retry |
…crum Adjust `memchr` pinning and run `cargo update` try-job: x86_64-mingw
Still haven’t gotten around to splitting this up, so be my guest as much as needed :) |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
PR's haunted. |
try-job: x86_64-mingw
Supersedes #129538