Snap store endpoints test is flaky
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and the only comment is the autogenerated Jira-sync bot message (CRAFT-3800), so it shows no sign of maintainer triage despite being 628 days old. The bug itself is real and well-documented (CI failure link, exact 1-second expiry mismatch), and the fix is straightforward (freeze/mock time in the test), so it should be triaged and kept open rather than closed as stale without evidence the test was fixed.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
21.25
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
20
Confidence:
75
Support Request:
0
|
close stale | Flaky test test_snap_store fails when load causes the generated expiry timestamp to drift by one second. Exact timestamp assertions trigger intermittent failures. Open and inactive for over a year, awaiting triage and a robust comparison fix. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.