Add configurable conversation timeout to all benchmarks #250
+12
−6
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
Apply the same timeout configuration from commit0 to all other benchmarks: - gaia - multiswebench - openagentsafety - swebench - swebenchmultimodal - swtbench Default timeout is 3600 seconds (1 hour), configurable via CONVERSATION_TIMEOUT env var. Co-authored-by: openhands <[email protected]>
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
Extends the timeout configuration from PR #235 (commit0) to all other benchmarks:
Changes
Each benchmark's
run_infer.pynow reads theCONVERSATION_TIMEOUTenvironment variable (default: 3600 seconds / 1 hour) and passes it toconversation.run(timeout=run_timeout).Notes
CONVERSATION_TIMEOUTenv varTesting
@simonrosenberg can click here to continue refining the PR