test: synchronize legacy automation race before interruption - #213
Merged
Conversation
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.
The legacy-client automation race test could interrupt its foreign Turn before the scripted Agent claimed the first step. The subsequent Automation then consumed that gated step and timed out instead of completing. This caused Python 3.12 to fail on the first main run after #212, despite the PR checks passing.
Wait for the foreign Agent to claim its step before interrupting it. All existing assertions remain, including refusal to adopt the foreign Turn and eventual completion with the Automation’s own Turn. Only seven test lines change; production code and timeouts are unchanged.
Validation:
This follow-up will be merged only after its applicable CI checks pass.