Snap store endpoints test is flaky
Metadata
Current evaluation
Flaky unit test tests/unit/test_endpoints.py::test_snap_store: expires timestamp differs by one second under load. Root-caused to the `expires` fixture; fix merged in PR #391 (c42cd69) but the issue was never closed.
Suggested action: close resolved
Reason: The root cause is the `expires` fixture in tests/unit/conftest.py: the expected value is built as `(now + timedelta(seconds=seconds)).replace(microsecond=0)` while craft_store/endpoints.py builds `(datetime.now(tz=timezone.utc).replace(microsecond=0) + timedelta(seconds=ttl)).isoformat()`, so a sub-second rounding difference under CI load produces the '00:00:22' vs '00:00:23' diff shown in the report. The most recent commit touching tests/unit/conftest.py and tests/unit/test_endpoints.py is c42cd69 "fix(test): make endpoint tests less flaky (#391)", a merged PR that adjusts those two test files to reduce endpoint-test flakiness in slow CI environments — i.e. the fix is already in the tree and the issue is only unclosed housekeeping. Impact is limited to CI noise (no library behaviour change), and the only comment is an autogenerated Jira-sync bot message, so no maintainer triage discussion exists.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
22
Complexity:
18
Confidence:
86
Actionability:
85
|
close resolved | Flaky unit test tests/unit/test_endpoints.py::test_snap_store: expires timestamp differs by one second under load. Root-caused to the `expires` fixture; fix merged in PR #391 (c42cd69) but the issue was never closed. | |
| qwen/qwen3.6-35b-a3b |
Impact:
20
Quick Win:
14
Complexity:
10
Confidence:
75
Actionability:
80
|
close resolved | Flaky test_snap_store test due to expires timestamp off by one second; fix merged in PR #391 but issue remains open | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
21
Staleness:
75
Complexity:
15
Confidence:
65
Support Request:
0
|
needs triage | Flaky unit test test_snap_store: token expiry timestamp can be off by one second under load, causing intermittent CI failures. Unlabeled, unassigned, no maintainer response since filing ~20 months ago; only a Jira-sync bot comment. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
5
|
needs triage | Flaky unit test for snap store endpoints where the generated token expiry timestamp differs by one second. Unassigned, unlabelled, and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
25
Confidence:
85
Support Request:
5
|
close stale | Flaky unit test test_snap_store fails due to a 1-second discrepancy in the generated token expiry timestamp. Open for over 1.5 years with no maintainer response or fix. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-store#391
(confidence 93%)
Merged PR 'fix(test): make endpoint tests less flaky' (commit c42cd69) is the newest commit on tests/unit/conftest.py and tests/unit/test_endpoints.py and adjusts those tests for slow CI.
-
Related To:
craft-store#241
(confidence 90%)
The issue body links the failing Actions job (runs/12286865000/job/34287817294?pr=241) from PR #241 'chore: move tests to starflow', the run where the flake was observed.
Related issues
No related issues found above the similarity threshold.