Skip to content

Sync dependencies between linkchecker and dist tarball#2451

Merged
bors-ferrocene[bot] merged 1 commit into
mainfrom
rachel/sync-linkchecker-deps
Jul 10, 2026
Merged

Sync dependencies between linkchecker and dist tarball#2451
bors-ferrocene[bot] merged 1 commit into
mainfrom
rachel/sync-linkchecker-deps

Conversation

@fs-rachel

Copy link
Copy Markdown
Contributor

No description provided.

@jyn514 jyn514 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the idea makes sense to me and i think this is "just" a bug. i'm confused that we never hit it in CI though ... could you spend a bit of time investigating whether we ever run the linkchecker?

let doc_out = builder.doc_out(host);

builder.ensure(Rustc::for_stage(builder, builder.top_stage, host));
//let compiler_doc_out = builder.compiler_doc_out(host); // For the future

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's this "for the future" thing? is this about another PR in flight?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This and moving doc_out into a different variable are to prepare for when we add links to the compiler docs. At the moment, they're built separately to the main docs and only get merged during the dist tarball build, so we'll need to mirror that logic across to the linkchecker to keep it happy.

But happy to remove this for now and put it back in when it's needed, if you'd prefer

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, let's keep the code the same and add a comment? that way this doesn't show as a change in the git history if i need to bisect it later.

let _guard = builder.msg_test("Linkcheck", bootstrap_host, 1);
let _time = helpers::timeit(builder);
linkchecker.delay_failure().arg(builder.out.join(host).join("doc")).run(builder);
linkchecker.delay_failure().arg(doc_out).run(builder);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why this change? i don't see doc_out used earlier.

@jyn514 jyn514 added the waiting-on-author If this PR was opened by an automation, the "author" is the assignee. label Jul 7, 2026
@fs-rachel

Copy link
Copy Markdown
Contributor Author

i'm confused that we never hit it in CI though ... could you spend a bit of time investigating whether we ever run the linkchecker?

The CI does run the linkchecker (it's under ferrocene/ci/split-tasks.py test:docs). But just before that, it fetches the coverage outcomes from a previous CI step, so they're already present

@fs-rachel fs-rachel added waiting-on-review and removed waiting-on-author If this PR was opened by an automation, the "author" is the assignee. labels Jul 8, 2026
@fs-rachel

fs-rachel commented Jul 8, 2026

Copy link
Copy Markdown
Contributor Author

Also the CI failure here is bizarre: the doctests failed, only on thumbv7em-ferrocene.facade-eabihf, and not because of a specific test failing but because

error: io error when listing tests: Os { code: 14, kind: Uncategorized, message: "Bad address" }

Not sure what to make of that, I'll rerun after updating the patchset (if needed) and see if it reoccurs

@jyn514

jyn514 commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

error: io error when listing tests: Os { code: 14, kind: Uncategorized, message: "Bad address" }

this is probably something to do with remote-test-server :/ it's less flaky than it used to be but still unreliable.

this LGTM other than the one comment i left above.

@jyn514 jyn514 added waiting-on-author If this PR was opened by an automation, the "author" is the assignee. and removed waiting-on-review labels Jul 8, 2026
@fs-rachel
fs-rachel force-pushed the rachel/sync-linkchecker-deps branch from d1eef30 to 09415f3 Compare July 8, 2026 16:47
@fs-rachel

Copy link
Copy Markdown
Contributor Author

@jyn514 How about this version?

@fs-rachel fs-rachel added waiting-on-review and removed waiting-on-author If this PR was opened by an automation, the "author" is the assignee. labels Jul 8, 2026
@Xylakant

Xylakant commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

error: io error when listing tests: Os { code: 14, kind: Uncategorized, message: "Bad address" }

this is probably something to do with remote-test-server :/ it's less flaky than it used to be but still unreliable.

This test is not (yet) running via remote-testserver. It does run under emulation, though, so qemu might be a culprit.

@jyn514 jyn514 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bors merge

@bors-ferrocene

Copy link
Copy Markdown
Contributor

Build succeeded:

@bors-ferrocene
bors-ferrocene Bot merged commit 31cd51a into main Jul 10, 2026
10 checks passed
@bors-ferrocene
bors-ferrocene Bot deleted the rachel/sync-linkchecker-deps branch July 10, 2026 19:41
@github-actions github-actions Bot added backport:maybe PR candidate for backport merged-in:1.98 labels Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants