-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
error_index_generator in 1.24.0 fails to build using 1.24.0, entity not found #48308
Comments
Looks like maybe we didn't generate the relevant metadata. Could you provide the full log by chance? |
This was seen on Fedora too, in the build.log here: |
To get away from distro idiosyncrasies, I tried default builds of stable, beta, and nightly, just pointing each to their matching |
I backported that commit to stable, without the unrelated stage0-diagnostic stuff, and it seems to work: |
Thanks for experimenting! Since it's looking like we might be releasing 1.24.1 anyway (due to a variety of regressions that where detected post-release) I'll try to make sure that patch makes it into that. |
triage: P-high Gotta get this fixed. |
[stable] 1.24.1 stable release The includes the following commits: - 6a600f8: Fixes #48251, unwinding through FFI no longer aborts - cuviper@b445a52: Fixes #48308, fixing the error index generator - f8e00d0: Fixes #48318 by emitting UTF-16 output on MSVC targets. - 2a0af8c448: Bumps the version number to 1.24.1. - 93220f0f45: Release notes - 6031718d8836f95bbfeddfaa63f1ee1d66e53f26: Cargo TLS warnings on Windows.
Fixed in 1.24.1. |
I can build rust 1.24.0 using our 1.23.0 package, but when I try to build 1.24.0 again using the 1.24.0 package I already built I get the following error during
python2 ./x.py install
:The text was updated successfully, but these errors were encountered: