-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Bump to 0.75.0; update changelog #12539
Conversation
r? @ehuss (rustbot has picked a reviewer for you, use r? to override) |
7a49c15
to
ac86772
Compare
Can't reproduce the resolver test failure. Could be a flaky test? @bors try |
Bump to 0.75.0; update changelog [rendered](https://github.com/weihanglo/cargo/blob/version-bump/CHANGELOG.md)
The resolver issue is #6258. I'm not sure what exactly is going on with that particular test. Maybe it needs more ticks to finish? Unfortunately due to its nature, there are pathological cases that can take an indefinite amount of time to finish, and proptesting can randomly hit those situations. |
It also looks like your try build hit another error:
I don't think I have seen that before. I'm not really sure what might have caused that. We should consider adding some more debug information to that test. |
Thanks! @bors r+ |
Bump to 0.75.0; update changelog [rendered](https://github.com/weihanglo/cargo/blob/version-bump/CHANGELOG.md)
💔 Test failed - checks-actions |
☀️ Test successful - checks-actions |
rendered