promote_firefox fails due to duplicated dependencies in task graph
Categories
(Firefox Build System :: Task Configuration, defect, P1)
Tracking
(firefox-esr102 unaffected, firefox-esr115 unaffected, firefox117 unaffected, firefox118 unaffected, firefox119blocking fixed)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox117 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | blocking | fixed |
People
(Reporter: jcristau, Assigned: jcristau)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
[Tracking Requested - why for this release]: breaks release promotion starting with beta 7
https://hg.mozilla.org/mozilla-central/rev/7453fae110a5 causes duplicate dependencies in partner-repack dummy tasks, which breaks the release promotion action.
Comment 1•1 year ago
|
||
:ahal, since you are the author of the regressor, bug 1839891, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Assignee | ||
Comment 2•1 year ago
|
||
Both the from_deps and release_deps transforms were adding the same task
as a dependency but under different keys. We don't actually need
release_deps for anything else here as far as I can tell, so skip it.
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
For the record this bug results in:
[task 2023-09-06T18:41:43.587Z] * method: createTask
[task 2023-09-06T18:41:43.587Z] * errorCode: InputValidationError
[task 2023-09-06T18:41:43.587Z] * statusCode: 400
[task 2023-09-06T18:41:43.587Z] * time: 2023-09-06T18:41:43.570Z
[task 2023-09-06T18:41:43.587Z]
[task 2023-09-06T18:41:43.587Z] Schema Validation Failed!
[task 2023-09-06T18:41:43.587Z] Rejecting Schema: https://firefox-ci-tc.services.mozilla.com/schemas/queue/v1/create-task-request.json#
[task 2023-09-06T18:41:43.588Z] Errors:
[task 2023-09-06T18:41:43.588Z] * data/dependencies should NOT have duplicate items (items ## 1 and 0 are identical)
Updated•1 year ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
bugherder |
Assignee | ||
Comment 6•1 year ago
|
||
Turns out the regressing change was merged to central after the bump to 119, so 118 is fine (https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=7453fae110a512c80d2ce4ef45596646d9ba52f4).
Description
•