🤖 fix: resolve flaky bash and web_search integration tests #713
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
- Decouple bash tool execution duration from network/AI latency - Use event timestamps to measure strict tool performance (<10s) - Relax overall test timeouts to prevent CI failures on slow runners - Lower reasoning effort for web_search test to improve speed
ammar-agent
force-pushed
the
fix/flaky-tests-pr701
branch
from
6a5d968 to
e396aac
Compare
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.
Generated with
muxFixes flaky integration tests observed in PR #701.
Changes:
thinkingLevelto 'low' to improve speed and reliability, and increased timeout to 180s.Verification:
tests/ipcMain/runtimeExecuteBash.test.tspasses locally.tests/ipcMain/openai-web-search.test.tspasses locally.