Flaky test: TestDockerSwarmSuite/TestSwarmVolumePlugin (daemon teardown exit status 130 on arm64)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 72.1k
- Forks
- 19.2k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 164
Description
Description
TestDockerSwarmSuite/TestSwarmVolumePlugin failed on arm64 during the integration-cli suite with the following error during daemon teardown:
check_test.go:631: [de0e5a1bd56e4] error while stopping the daemon: exit status 130
--- FAIL: TestDockerSwarmSuite/TestSwarmVolumePlugin/stop-de0e5a1bd56e4 (22.01s)
--- FAIL: TestDockerSwarmSuite/TestSwarmVolumePlugin (58.14s)
Exit status 130 indicates the daemon was killed by SIGINT. This occurs during the per-test daemon teardown phase (stop-<id>), suggesting a timing issue where the daemon does not shut down cleanly within the expected window.
Evidence
| Run | Branch | Job | Result |
|---|---|---|---|
| 32065644308 | master | test (arm64, snapshotter) / integration-cli (DockerSwarmSuite) | ❌ FAIL |
| 32074655290 | master | test (arm64, snapshotter) / integration-cli (DockerSwarmSuite) | ✅ PASS |
| 32053410803 | renovate branch | test (arm64, snapshotter) / integration-cli (DockerSwarmSuite) | ✅ PASS |
| 32033810507 | bump_testify | test (arm64, snapshotter) / integration-cli (DockerSwarmSuite) | ✅ PASS |
The test fails in 1/4 observed runs — confirmed flaky.
Classification
- Flaky: Yes (passes in ≥1 independent run, fails in ≥1 independent run)
- Platform: arm64
- Test suite:
integration-cli,TestDockerSwarmSuite - Failure mode: Daemon teardown timeout —
stop-<container_id>exits 130 (SIGINT-killed)
Notes
The failure is in the TearDown helper (not the test logic itself), meaning the swarm daemon is not shutting down within the allotted time during cleanup after TestSwarmVolumePlugin. This pattern is similar to other swarm daemon teardown flakes (see #33041, #32173).
cc @vvoland
Flagged by automated CI flakiness scan.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with integration-cli's TestDockerSwarmSuite/TestSwarmVolumePlugin and the per-test TearDown path, including check_test.go:631 where daemon stopping fails. Reproduce the arm64 failure and compare the related swarm teardown flakes in #33041 and #32173; done means the daemon teardown completes reliably and the test passes on the affected suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100