test(s3): aim collection force-delete at the master the suite actually runs (#10404)

The copying and tagging tests force-drop each bucket's collection at the master so volume slots are freed deterministically between tests. But the copy-tests CI job runs its master on 9336 and the tagging Makefile on 9338, while the tests default to 9333 — the cleanup dialed a dead port and quietly no-oped. Each test bucket then grows 7 volumes against -volume.max=100, and whenever async deletion lagged the data node ran out of slots and PutObject 500ed with "No writable volumes and no free volumes left". Set MASTER_ENDPOINT where the master port is non-default: the copy-tests workflow step, and the copying/tagging Makefiles (derived from MASTER_PORT).
2026-07-25 01:22:39 +00:00 · 2026-07-22 21:37:59 -07:00
parent 5731f37a2f
commit 2e9b944e5c
3 changed files with 7 additions and 1 deletions
@@ -765,7 +765,7 @@ jobs:
            sleep 2
          done
          
-          go test -v
+          MASTER_ENDPOINT="http://127.0.0.1:9336" go test -v
          kill -9 $pid || true
          # Clean up data directory
          rm -rf "$WEED_DATA_DIR" || true