Repository navigation
ci(canary): give the doctor backend-source step a 120 s probe timeout (#968) - #971
Merged
Merged
Conversation
…#968) The step asserts where CodeLLDB resolves from; a rust row that timed out carries no backend.source to assert on. doctor is the first thing to run each toolchain on a fresh runner, and on windows-latest the same published 0.25.1 took 5-6 s for this step on 2026-09-29, 11-15 s on 09-30, 12-27 s on 10-13 and 36-37 s on 10-20, when rust's probe passed 30 s. The doctor fix in #968's other PR reaches this job only with the next release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y3ULnoVSoCZ5t2Y8d98Ctv
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #968, alongside #970. Workflow-only change, so no changelog fragment.
The canary step "Assert CodeLLDB backend source (doctor)" checks where the published CLI resolves CodeLLDB from. On 2026-10-20 it failed on
npm default (windows-latest): doctor's rust probe hit the step's own--timeout 30000, and a timed-out rust row has nobackend.sourceto check.doctor is the first thing that runs each toolchain on a fresh runner. On Windows, the same published 0.25.1 took this long for this step:
This PR raises the step's timeout to 120 s and adds a comment explaining why. #970 makes doctor probe a named language on its own, but the canary installs the published package, so it sees #970 only after the next release. Without this change, every weekly run until then fails the same way.
Left as is:
scripts/canary-smoke.mjs's 30 s request timeout, which was #789's failure point. doctor runs before it and warms the toolchains: on 2026-10-20 the firstlist_supported_languagesafter doctor finished inside a 4 s smoke cycle.Verification:
mainwithchannels=npmand watch the two Windows legs.🤖 Generated with Claude Code
https://claude.ai/code/session_01Y3ULnoVSoCZ5t2Y8d98Ctv