-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[experiment] Update cc
CI tests
#130908
[experiment] Update cc
CI tests
#130908
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
@bors try |
[experiment] Update cc to 1.0.100 See rust-lang#130720, rust-lang#130898; try with the minimal version bump. try-job: x86_64-msvc
☀️ Try build successful - checks-actions |
Woah! So it succeeded with 1.0.100, let's try the next one up. |
@bors try |
[experiment] Update cc to 1.0.100 See rust-lang#130720, rust-lang#130898; try with the minimal version bump. try-job: x86_64-msvc
Probably should have done more of a bisect algorithm, since we have (now) a known good at 1.0.100 and a known bad at 1.0.106. Updated to 1.0.103, I think the first job will still continue @bors try |
[experiment] Update cc to 1.0.100 See rust-lang#130720, rust-lang#130898; try with the minimal version bump. try-job: x86_64-msvc
1.0.105 and 1.0.106 both have windows changes, so those seem like likely candidates https://github.com/rust-lang/cc-rs/releases/tag/cc-v1.0.105 https://github.com/rust-lang/cc-rs/releases/tag/cc-v1.0.106. I guess if try jobs work in parallel, might as well make use of that. @bors try (for 1.0.104) |
cc
CI tests
[experiment] Update cc to 1.0.100 See rust-lang#130720, rust-lang#130898; try with the minimal version bump. try-job: x86_64-msvc
@bors try (for 1.0.105) |
[experiment] Update `cc` CI tests See rust-lang#130720, rust-lang#130898; try with the minimal version bump. try-job: x86_64-msvc
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
So we have:
All of the failures were around the 1 hour mark, failure to build The changes between 1.0.100 and 1.0.101 did adjust the way that some tools are found on Windows, maybe the update causes different versions to be located? That may also make a caching difference rust-lang/cc-rs@cc-v1.0.100...cc-v1.0.101 These results don't feel very concrete so I'll rerun 100/101 to see if they appear consistent. |
@bors try |
[experiment] Update `cc` CI tests See rust-lang#130720, rust-lang#130898; try with the minimal version bump. try-job: x86_64-msvc
☀️ Try build successful - checks-actions |
I think this commit is suspicious. I would like to try without it. |
Trying with 1.1.22, which includes @ChrisDenton's fix rust-lang/cc-rs#1215 @bors try |
[experiment] Update `cc` CI tests See rust-lang#130720, rust-lang#130898; try with the minimal version bump. try-job: x86_64-msvc
It looks like that fix works. |
Did it pass somewhere? It looks like the try jobs here and in #130926 only got picked up 25 minutes ago |
The job has built |
Everything gets built multiple times, the failures here have been around the 1 hour mark. Some of the MSVC issues are closer to the end though. |
☀️ Try build successful - checks-actions |
Cool, Chris has the update covered in #130926 (comment) |
See #130720, #130898; try with the minimal version bump.
try-job: x86_64-msvc