1647219 - mobile retrigger-multiple shouldn't be considered a rerun, fails if task past deadline (1 day)

Status: NEW

(Release Engineering :: General, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://treeherder.mozilla.org/#/jobs?repo=reference-browser&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=b62b26e6ecfad8d0c69d5c2b48c4381fe5969b83&selectedTaskRun=IJXf2Ws_SUC4wSnqaJYivg.0 is a retrigger of a debug(ui-test-x86) task but failed:

Log: https://treeherder.mozilla.org/logviewer.html#?job_id=307035012&repo=reference-browser
HTTPError: 409 Client Error: Conflict for url: http://taskcluster/api/queue/v1/task/AfbfPb77Tb-iVnSCEDFx7A/rerun

Analysis from jlorenzo: [The failure is] retrigger-multiple is considered to be a rerun.

Comment 1

[Aki Sasaki (not active)]

So in https://hg.mozilla.org/ci/taskgraph/file/tip/src/taskgraph/actions/retrigger.py#l269 we automatically decide whether to rerun or retrigger tasks (e.g. release tasks should be rerun). There is no way to force-retrigger, nor am I certain that we want to. However, I certainly don't see us wanting to automatically rerun ui tests, so maybe that is the bug: ui tests should be retriggered instead of rerun (except in PRs, where the PR checks won't go green unless we rerun =\ ).

Comment 2

[BMO Github Automation]

Attachment: [mozilla-mobile/reference-browser] Bug 1647219 - let tests get retriggered rather than rerun (#4186)