cloudfoundry / cloudfoundry/routing-release
cfsmoke tests are unstable
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 176
- Forks
- 114
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 6
Description
Current behavior
Test fail regularly with the same error, e.g. https://ci.funtime.lol/teams/wg-arp-networking/pipelines/routing-release/jobs/run-cfsmoke/builds/269:
[FAILED] in [AfterEach] - /var/vcap/packages/smoke_tests/src/smoke_tests/smoke/isolation_segments/isolation_segment.go:75 @ 02/05/26 21:13:03.83
<< Timeline
[FAILED] Timed out after 30.000s.
Expected process to exit. It did not.
In [AfterEach] at: /var/vcap/packages/smoke_tests/src/smoke_tests/smoke/isolation_segments/isolation_segment.go:75 @ 02/05/26 21:13:03.83
------------------------------
•••
Summarizing 1 Failure:
[FAIL] RoutingIsolationSegments [AfterEach] When an app is pushed to a space that has been assigned the shared isolation segment is not reachable from the isolation segment router
/var/vcap/packages/smoke_tests/src/smoke_tests/smoke/isolation_segments/isolation_segment.go:75
Ran 4 of 4 Specs in 109.877 seconds
FAIL! -- 3 Passed | 1 Failed | 0 Pending | 0 Skipped
Ginkgo ran 3 suites in 1m49.898900119s
There were failures detected in the following suites:
isolation_segments ./smoke/isolation_segments
Test Suite Failed
[WARN tini (1)] Reaped zombie process with pid=20
Error: failed to run job-process: exit status 1 (exit status 1)
Desired behavior
(more) stable test.
Affected Version
all
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 smoke/isolation_segments/isolation_segment.go, especially the AfterEach failure at line 75, and run the isolation_segments suite at ./smoke/isolation_segments. Compare the recurring timeout in the linked CI build with the suite's behavior; done means the cfsmoke test no longer fails intermittently and remains reliable across runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100