Closed
Bug 1517662
Opened 6 years ago
Closed 6 years ago
Fix flaky tests
Categories
(Taskcluster :: General, enhancement)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
https://tools.taskcluster.net/groups/T0ReJs1wTjmTNtQnEq0rQg/tasks/LqwOwac-RkqBJZVZH4lTXA/runs/0/logs/public%2Flogs%2Flive_backing.log
Our guess is that this is due to the same test suite running twice at the same time.
|
Assignee | |
Comment 2•6 years ago
|
||
index: https://tools.taskcluster.net/groups/aMWpi6bPRD6mCZGp_l87bw/tasks/LBr88qtHQSasavurR1A30Q/details
index: https://tools.taskcluster.net/groups/FoDr2gucR2Or3xaGMuyVSw/tasks/Q8vadtZqSkGcEAlSpp9Pug/details
index: https://tools.taskcluster.net/groups/aWsW4V1LTgOu-UIPQ_uqLA/tasks/HaaZvQuxQ9u9Ox6wloiQrw/details
queue: https://tools.taskcluster.net/groups/aMWpi6bPRD6mCZGp_l87bw/tasks/Flqvdf4_R2yZrPkX-t9lHA/details
queue: https://tools.taskcluster.net/groups/cSDUg48GShCsI-Bp4aovbQ/tasks/N3EUz4QvSSiy3SUim7QA1w/details
queue: https://tools.taskcluster.net/groups/aWsW4V1LTgOu-UIPQ_uqLA/tasks/ULGeNagTTN6vrVcZDHoT2w/details
secrets: https://tools.taskcluster.net/groups/aWsW4V1LTgOu-UIPQ_uqLA/tasks/DNloQ4qiQeqwqBnSvFmnvA/details
hooks: https://tools.taskcluster.net/groups/FoDr2gucR2Or3xaGMuyVSw/tasks/Dzccgv8bR7KFkonGfHmBDQ/details
notify: https://tools.taskcluster.net/groups/aWsW4V1LTgOu-UIPQ_uqLA/tasks/HvNQKA3uT6WxQhQtP3Dxhw/details
|
|
Assignee | |
Comment 3•6 years ago
|
||
https://github.com/taskcluster/taskcluster/pull/51 should fix all of those, at least.
|
|
Assignee | |
Comment 4•6 years ago
|
||
This push was green on master, so that's good at least. I'll keep this open for a bit more, and we can link any additional flaky failures here.
|
|
Assignee | |
Comment 5•6 years ago
|
||
|
|
Assignee | |
Comment 6•6 years ago
|
||
|
|
Assignee | |
Updated•6 years ago
|
Summary: Fix flaky hooks tests → Fix flaky tests
|
|
Assignee | |
Comment 7•6 years ago
|
||
I reproduced the first one of those as a service timeout (503) in the auth service. That takes 30 seconds, during which time the test fails and tc-client automatically retries the request and it goes OK. There have only been four 503's in the last 24h, and I think three of them were from this test (which, admittedly, I was running in a tight loop). I'll chalk that up to service flakiness and Azure flakiness.
|
|
Assignee | |
Comment 8•6 years ago
|
||
|
|
Assignee | |
Comment 9•6 years ago
|
||
I think we're in good shape -- no complaints for a week. Let's open new bugs if we find any additional flakiness (such as bug 1521796)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•