This repository was archived by the owner on Oct 9, 2026. It is now read-only.
Repository navigation
Conversation
Contributor
Author
|
Superseded by #63, which includes this change or replaces it. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
TestAgentLoop_Steering_SkipsRemainingToolsfailed on windows-latest in run 37566619049 on main: "timeout waiting for tool_one to start", after 2.25 s.It's the cause #28 found for
TestRunTurn_HardAbort. On that runner a turn's setup took 2 to 4 s, and the test allowed 2 s for the turn to set up, call the model and start the tool. Its other waits insteering_test.gomake the same bet: 1 to 5 s for the first model call to start, a tool to start,Runto stop, a reply to arrive, or the turn to finish.Every wait in the file for something that must happen now uses one limit,
steeringWait, 10 s. Only a failing test waits that long, so passing runs take the time they did. The two 10 ms polling ticks stay, and so does the 300 ms check that nothing more arrives after/stop. That one asserts an absence, so a longer wait would only slow it down.Test only; no CHANGELOG line.