Repository navigation
fix(release): isolate source qualification workspace tests - #6160
Merged
Astro-Han merged 1 commit intoOct 19, 2026
Merged
Conversation
Generated-by: Codex
Sun-GLiang
approved these changes
Oct 19, 2026
4 of 6 tasks
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
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.
Summary
Source qualification runs the Runtime Host suite alongside two other workspaces. At
0b9204b1f, two complete attempts failed differently: the owned-Host startup test missed its 6-second election window, then the event-wait suite stalled until the 15-minute workspace limit. Normal CI runs Runtime Host separately and passed at that commit; both affected files also pass in isolation locally (11 and 251 tests).Use the existing workspace scheduler override,
npm test -- --concurrency=1, in the source-candidate workflow. Each workspace retains its own test-file concurrency. All workspaces, assertions, startup deadlines, and the workspace timeout remain unchanged. This removes cross-workspace resource contention during qualification without changing product code. The full extracted-source workflow must still pass after merge; the isolated checks alone do not qualify an RC or prove every timing issue resolved.Also record the Composer selector change from #6158, which landed on main while the 0.2.2 qualification was running.
Refs #6148, #6159.
Failed qualification attempts: https://github.com/apache/maka/actions/runs/39200805088
Verification
npm run format,npm run lint, andgit diff --checkpassed.AI use
Tool(s) and scope: Codex investigated the two qualification failures, updated the workflow and release note, and ran the targeted checks.
Checklist
Does this PR entail a change in behavior?