Summary
The integration subtest TestRecommendationCompletenessCommand/savingsplans-database/api-error (cmd/recommendation_completeness_test.go, added in #2130) failed once in CI on a docs-only PR branch, then passed on a rerun of semantically identical code.
Evidence
A docs-only change cannot affect this test, so the failure indicates nondeterminism in the test or its fixtures (timing, map iteration order, or simulated API-error propagation).
Expected behaviour
The subtest is deterministic: same inputs, same verdict, every run.
Suggested investigation
- Run the subtest in a loop with
-count=50 -shuffle=on locally to reproduce.
- Check for map-order dependence in the synthetic operation counts logged by the test (
synthetic operations=map[...]) and for timing assumptions in the api-error path.
Summary
The integration subtest
TestRecommendationCompletenessCommand/savingsplans-database/api-error(cmd/recommendation_completeness_test.go, added in #2130) failed once in CI on a docs-only PR branch, then passed on a rerun of semantically identical code.Evidence
--- FAIL: TestRecommendationCompletenessCommand/savingsplans-database/api-error (1.26s).A docs-only change cannot affect this test, so the failure indicates nondeterminism in the test or its fixtures (timing, map iteration order, or simulated API-error propagation).
Expected behaviour
The subtest is deterministic: same inputs, same verdict, every run.
Suggested investigation
-count=50 -shuffle=onlocally to reproduce.synthetic operations=map[...]) and for timing assumptions in the api-error path.