-
Notifications
You must be signed in to change notification settings - Fork 13k
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
rustdoc ICE: no resolutions for a doc link #109424
Comments
rustc
panic when running cargo doc
on a project
This may have been fixed by #109266. Does it work on the most recent nightly? |
it was ok in |
I am seeing a similar ICE: Backtrace and cargo error
whose repro is creating a dependency on |
https://github.com/bytecodealliance/rustix/blob/5caa325f24cbb421c54fb4416c21888865a0c3b1/src/io/read_write.rs#L14 is the line which the ICE occurs on. bytecodealliance/rustix#539 removed this line which is why the ICE goes away BisectionRegression in rust-lang-ci@6cfb8fd -> #109266 bisected with cargo-bisect-rustc v0.6.5Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc 2023-03-19 --end 2023-03-23 --regress=ice --script=script.sh |
For reference, I think this regression could be a @rustbot label -I-prioritize +P-high |
Potentially solved by #109330 |
Nightly is currently running into ICEs (possibly rust-lang/rust#109424) and it's not worth breaking CI for an index page.
Nightly is currently running into ICEs (possibly rust-lang/rust#109424) and it's not worth breaking CI for an index page.
Update rustix with `cargo update -p rustix`. This should work around the ICE that happens when running `cargo doc` on CI: https://github.com/prisma/prisma-engines/actions/runs/4915235114/jobs/8777494487. The ICE is already fixed in beta and nightly but not in stable yet (rust-lang/rust#109424). Newer versions of rustix than we have don't trigger the bug because it was worked around in bytecodealliance/rustix#627.
Update rustix with `cargo update -p rustix`. This should work around the ICE that happens when running `cargo doc` on CI: https://github.com/prisma/prisma-engines/actions/runs/4915235114/jobs/8777494487. The ICE is already fixed in beta and nightly but not in stable yet (rust-lang/rust#109424). Newer versions of rustix than we have don't trigger the bug because it was worked around in bytecodealliance/rustix#627.
resolve: Preserve reexport chains in `ModChild`ren This may be potentially useful for - avoiding uses of `hir::ItemKind::Use` (which usually lead to correctness issues) - preserving documentation comments on all reexports, including those from other crates - preserving and checking stability/deprecation info on reexports - all kinds of diagnostics The second commit then migrates some hacky logic from rustdoc to `module_reexports` to make it simpler and more correct. Ideally rustdoc should use `module_reexports` immediately at the top level, so `hir::ItemKind::Use`s are never used. The second commit also fixes issues with rust-lang/rust#109330 and therefore Fixes rust-lang/rust#109631 Fixes rust-lang/rust#109614 Fixes rust-lang/rust#109424
Code
Panic occurs when running
cargo doc
on my project here. This is specifically on the currenttransfer
branch of the project with commit hash c1d04db7977d2de43d69ea9f8795905f60b3b8ba. Note that this project does include theCargo.lock
file, and that the project compiles normally (i.e. withcargo build
) just fine.Meta
cargo --version --verbose
:rustc --version --verbose
:Error output
There are numerous panics when running
cargo doc
, but the first one seems to happen whileChecking serde_json v1.0.94
:Backtrace
The text was updated successfully, but these errors were encountered: