Skip to content

[DO NOT MERGE] ci(swtbench): revert to Blacksmith runner (fallback for #495)#673

Draft
simonrosenberg wants to merge 1 commit into
mainfrom
openhands/swtbench-revert-to-blacksmith-495
Draft

[DO NOT MERGE] ci(swtbench): revert to Blacksmith runner (fallback for #495)#673
simonrosenberg wants to merge 1 commit into
mainfrom
openhands/swtbench-revert-to-blacksmith-495

Conversation

@simonrosenberg
Copy link
Copy Markdown
Collaborator

⚠️ DO NOT MERGE — fallback branch only

Parallel to #672 (the real fix). Keeps a known-good configuration on hand to dispatch against if the docker rmi + free-disk-space + preflight approach in #672 doesn't hold up under real load.

What this does

Surgical revert of the swtbench portion of #651: puts build-swtbench-images.yml back on blacksmith-32vcpu-ubuntu-2204 + useblacksmith/setup-docker-builder@v1. Everything added since — notably the workflow_call trigger + cross-repo checkout from #666 — is preserved.

Why this "works"

Blacksmith runners have hundreds of GB of persistent disk, which masks the underlying bug in assemble_agent_image (local images retained after push). The bug is still there; the runner just has enough headroom that 433 images don't fill it.

So this is explicitly not the fix — it's the "revert the migration" escape hatch. The real fix is #672.

Relationship to other work

AI disclosure

This PR was prepared by Claude (Claude Code) on behalf of @simonrosenberg.

Surgical revert of the swtbench portion of #651 — puts the SWT-bench
image-build workflow back on blacksmith-32vcpu-ubuntu-2204 with the
useblacksmith/setup-docker-builder builder. Blacksmith's larger
persistent disk masked the unbounded local-image growth that now
fails on ubuntu-latest-8core (evaluation#495).

Kept intact from main:
- workflow_call trigger and cross-repo checkout (#666)
- all input/env plumbing and downstream steps

Intended as a parallel fallback branch while the real fix in #672
(docker rmi after push + free-disk-space + preflight) is validated.
@simonrosenberg
Copy link
Copy Markdown
Collaborator Author

@juanmichelini

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant