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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swe bench results #549
Swe bench results #549
Changes from 6 commits
06bf194
606acc1
c39e670
903e8d5
0ecf587
e98b4e4
e84838d
bbf9e3b
f7d459b
3c522f7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider adding a
try-except
block aroundbenchmark.run(retries=retries)
to catch and handle any exceptions that might occur during the execution of a benchmark. This would allow the benchmarking process to continue even if one benchmark fails, improving the robustness of the benchmark runner.Handling exceptions in this manner ensures that the benchmarking process is not halted due to a single failure, providing a more resilient and user-friendly experience.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After the loop that processes each benchmark, it would be useful to log the total number of benchmarks processed and how many were skipped due to reaching the
max_benchmarks
limit. This information could be valuable for users to understand the scope of the benchmark run and ensure transparency.Including such logging can enhance the user's understanding of the benchmarking process and provide insights into the execution flow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After the loop that processes each benchmark, it would be useful to log the total number of benchmarks processed and how many were skipped due to reaching the
max_benchmarks
limit. This information could be valuable for users to understand the scope of the benchmark run and ensure transparency.Including such logging can enhance the user's understanding of the benchmarking process and provide insights into the execution flow.