firefox-android legacy-arm tasks often retried until exception hit because SM-G950F, API Level 28 platform has inconclusive results
Categories
(Firefox Build System :: Task Configuration, defect)
Tracking
(firefox113 fixed)
Tracking | Status | |
---|---|---|
firefox113 | --- | fixed |
People
(Reporter: aryx, Assigned: aaronmt)
References
Details
Attachments
(1 file)
The legacy-arm tasks of the firefox-android repository often get retried or fail with an exception after 5 retries. 3 of 3 such failures investigated had inconclusive results for the SM-G950F, API Level 28 platform (example). Inconclusive results for this platform in its current state should not trigger reruns.
Transferring NI to :aaronmt. QA owns the UI tests jobs[1]. I'm happy to provide more info if the builds happen to be broken in some way 🙂
Assignee | ||
Comment 2•2 years ago
•
|
||
The SM-G950F dreamlte
is high capacity so it's not a queuing issue, but rather an infra problem with the device on Firebase Test Lab. I've posted in their Slack (I see another similar comment there). We can remove the device from the Flank configuration in the next day if need be, but these tests are not blocking.
Assignee | ||
Comment 3•2 years ago
|
||
From Firebase Community Slack
Hi Aaron, this appears be an issue with a recent release of Google Play Services (com.google.android.gms) on this particular device. We have an engineer digging deeper into the problem.
No ETA. We can remove the dreamlte
in the meantime.
Comment 4•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Updated•2 years ago
|
Comment hidden (Intermittent Failures Robot) |
Description
•