fix(swtbench): prevent build workflow from hanging indefinitely #403
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
This PR addresses issue #400 where SWT-Bench image build workflows were hanging indefinitely (2+ hours) at the "Build and push SWT-Bench images" step, blocking evaluation runs.
Problem
SWT-Bench builds after 14:12 UTC on 2026-02-06 were freezing with no progress updates, while earlier builds completed successfully in ~10 minutes. The builds were consuming runner resources indefinitely and blocking evaluation pods.
Root Cause Analysis
Comparing the SWT-Bench workflow with the working SWE-Bench workflow revealed several missing safeguards:
Changes
Add preflight step to prune BuildKit cache and verify disk space
build-swebench-images.ymlAdd timeout-minutes to build steps
Add BUILDKIT_RESET_ON_FAILURE=1 environment variable
Change concurrency group to global (not per-ref)
cancel-in-progress: trueto cancel old runs when new ones startTesting
This is a workflow configuration change. The fix will be validated when the workflow runs in GitHub Actions. The changes align with the working SWE-Bench workflow configuration.
Fixes #400
@juanmichelini can click here to continue refining the PR