Reading issue
rust-lang / rust · Issue No. 163011
I tried running ./x.py test locally and got this error:
Building stage1 linkchecker (stage0 -> stage1, x86_64-unknown-linux-gnu)
Finished `release` profile [optimized + debuginfo] target(s) in 0.22s
Testing stage1 Linkcheck (x86_64-unknown-linux-gnu)
reference/print.html:15697: broken link - `core/convert/enum.Infallible.html`
reference/print.html:58792: broken link - `core/convert/enum.Infallible.html`
reference/crates-and-source-files.html:633: broken link - `core/convert/enum.Infallible.html`
reference/types/never.html:563: broken link - `core/convert/enum.Infallible.html`
checked links in: 46.2s
number of HTML files scanned: 62405
number of HTML redirects found: 22249
number of links checked: 2983027
number of links ignored due to external: 186456
number of links ignored due to exceptions: 31
number of intra doc links ignored: 9
errors found: 4
NOTE: if you are adding or renaming a markdown file in a mdBook, don't forget to register the page in SUMMARY.md
found some broken links
Command `/usr/local/google/home/aliceryhl/rust/build/x86_64-unknown-linux-gnu/stage1-tools-bin/linkchecker /usr/local/google/home/aliceryhl/rust/build/x86_64-unknown-linux-gnu/doc` failed with exit code 1
Created at: src/bootstrap/src/core/build_steps/tool.rs:1627:23
Executed at: src/bootstrap/src/core/build_steps/test.rs:224:77
Command has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 0:46:18
Relay reads this issue against the repository's contribution signals: the files it is likely to touch, how the maintainers triage work this size, and what the first contribution would exercise.
The full analysis for this issue is still being assembled. Until then, the description above and the thread on GitHub are the most reliable context.