-
Notifications
You must be signed in to change notification settings - Fork 198
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
build failures with no entry found for key
panics
#1632
Comments
There is not a noticeably higher percentage of build failures over the last day or two, so it seems like it's not a very common failure. There's a pretty small fix PR already posted, so we can queue rebuilds for the crates impacted in a couple days when that is released to nightly. |
(Speaking of, it'd be useful to have some scripting to grep recent build logs so we can find all impacted crates/versions). |
I guess I'm affected by the same problem: https://docs.rs/crate/num-prime/0.1.0/builds/501949 |
The original issue was marked fixed, but there's still a panic with |
So it sounds like there are multiple sources of this ICE, just in case the specific issues these crates hit are fixed I've requeued builds for |
Only |
I did a little grepping and grabbed all other builds that hit this issue in the last few days
|
Hopefully the upstream bug is fixed now? |
Requeued the crates that have been mentioned ( |
|
@Nemo157 there is a new failure reported (by @TheDarkula ) is it worth requeuing? |
Yep, that build was before the last fix so might succeed, I've requeued it. |
@TheDarkula can find the queue here, rebuilds are lowest prio. Looking at https://docs.rs/crate/themelio-stf/0.9.7/builds it actually looks like the build passed now. |
Fantastic! |
Now that we have a new fix I have requeued retina and holochain, and they've both already completed successfully. Since there's no more specific known failures I've also requeued the other 95 matching build failures at a lower priority (also so we can see whether any of them fail again to give another testcase). other queued crates
|
Crate names
Build failure links
Additional details
Looks like there's been a recent regression in nightly rustdoc that affects more than just my crate. These look related:
Is it possible/worthwhile to pin
docs.rs
to an older nightly until this is fixed?The text was updated successfully, but these errors were encountered: