-
Notifications
You must be signed in to change notification settings - Fork 2.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
regression in README parsing #8351
Comments
I'll take a look. |
Just going to reopen until the next nightly is published. |
Yup. We saw this in our CI/CD systems this morning. Caused quite a stir and a ton of lost time debugging until we realized it was the nightly version. Unfortunate this crept in. Are the no tests for this regression in place? Should we add them? |
A smoke test is being added in rust-lang/rust#73267 to catch issues like this. |
In the most recent nightly build of cargo a regression slipped in around handling of READMEs in published crates [1]. Unfortunately this breaks CI builds because a 3rd level dependency (pyo3->inventory->ctor) triggers this regression. The issue has been corrected in cargo and the next nightly should fix this. However, to unblock things in the meantime this commit pins the nightly version to a known working version. We can simply revert this after the fix has been released. [1] rust-lang/cargo#8351
Fixes #1380 Working around rust-lang/cargo#8351
This should be fixed now. |
Update
This has been fixed and the next nightly (2020-06-13) should contain the fix assuming rust-lang/rust#73266 lands. Nightly releases are usually published around 00:30 to 01:00 UTC.
Original issue
As of rust-lang/rust#73198 (presumably #8277), Cargo fails to find README in some published crates, leading to failures at build time:
Reproduction:
Note that this hasn't hit nightly yet but it's likely too late to revert it before it does. This is breaking rustc-perf at least (and probably lots of other places that depend on crates published without READMEs included).
The text was updated successfully, but these errors were encountered: