Closed Bug 1547781 Opened 5 years ago Closed 5 years ago

Actions can generate tasks depending on nonexistent tasks

Categories

(Firefox Build System :: Task Configuration, task)

task
Not set
normal

Tracking

(firefox68 fixed)

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: dustin, Assigned: dustin)

Details

Attachments

(2 files)

https://tools.taskcluster.net/groups/LgTem2mQRc-wrUncuVKzgg/tasks/bkK7CuVWSAuVfHokJ_6x9w/runs/0/logs/public%2Flogs%2Flive.log

[task 2019-04-29T17:41:13.049Z] Creating task with taskId K_bZv4DTTo-psbnlRYrjoQ for test-windows10-64-qr/opt-raptor-tp6-9-firefox-e10s
[task 2019-04-29T17:41:13.994Z] `task.dependencies` references non-existing tasks: 
[task 2019-04-29T17:41:13.995Z]  * SuqKt1ZCTuC-0X-flKkSKQ,
[task 2019-04-29T17:41:13.995Z] All taskIds in `task.dependencies` **must** exist
[task 2019-04-29T17:41:13.995Z] before the task is created.

According to the decision task's label-to-taskid.json, SuqKt1ZCTuC-0X-flKkSKQ is a build-win64/opt task. But it does not, in fact, exist. The decision task ran on March 12, and the build job had a 28-day retention, so that all fits.

I suppose we should make try decision tasks disappear after 28 days, too.

This ensures that the artifacts an action task might consult will be gone at
the same time that the push's tasks expire.

Depends on D29269

Pushed by dmitchell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/80a1bc138c4f
test that .taskcluster.yml renders; r=Callek
https://hg.mozilla.org/integration/autoland/rev/1fb59fab2d6b
expire try decision artifacts after 28 days r=Callek
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: