-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Description
I try to run the SWE-Bench verified with minimax-m2.1, and there are some errors like:
Instance django__django-12663 - 2026-01-20 21:56:40,853 - WARNING - [child] Instance django__django-12663 failed (attempt 2/3): Conversation run failed for id=c53b0c68-aa0c-496c-98ff-9eea673f5557: Run timed out after 3600.0 seconds. The conversation may still be running on the server.
Instance django__django-13121 - 2026-01-20 21:57:03,152 - WARNING - [child] Instance django__django-13121 failed (attempt 2/3): Conversation run failed for id=1bc5f1b8-c88f-46b6-8ec5-401f5ec0758f: Run timed out after 3600.0 seconds. The conversation may still be running on the server.
Instance django__django-13033 - 2026-01-20 21:57:05,000 - WARNING - [child] Instance django__django-13033 failed (attempt 2/3): Conversation run failed for id=8138b6bb-f926-43c7-b279-e7aed34ca3fa: Run timed out after 3600.0 seconds. The conversation may still be running on the server.
And the evaluation shows there are some empty_patch_instances and error_instances:
> # head output.report.json
{
"total_instances": 500,
"submitted_instances": 499,
"completed_instances": 390,
"resolved_instances": 265,
"unresolved_instances": 125,
"empty_patch_instances": 103,
"error_instances": 6,
"completed_ids": [
"astropy__astropy-12907",
How to solve these?
Metadata
Metadata
Assignees
Labels
No labels