ci: stabilize native integration tests on slower runners - #149
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
Signed-off-by: rldyourmnd <danil@nddev.it.com>
rldyourmnd
changed the title
Signed-off-by: rldyourmnd <danil@nddev.it.com>
This was referenced Sep 13, 2026
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
1 participant
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.
The native Intel macOS lane hit two independent fixture limits: the aggregate Go package budget, and a 350 ms Python startup deadline that could expire before the escaped child existed. Give the suite a bounded 15-minute budget inside its 20-minute job and wait for the child readiness file before testing cancellation ownership. The timeout cleanup test remains separate; production deadlines and cleanup semantics are unchanged.
Validation: actionlint and the real process-group tests under
go test -race ./core/app -run ^TestDeclared -count=1passed. Failed runs 34728722224 and 34731142815 remain recorded. Only CI/test files change; the released 0.9.4 runtime payload is unchanged.