GCP Alert: duplicate key value violates unique constraint due to duplicate mozharness-action JSONs
Categories
(Testing :: Performance, defect, P2)
Tracking
(Not tracked)
People
(Reporter: sparky, Unassigned)
References
Details
(Whiteboard: [fxp][operational])
There are currently duplicate mozharness-action perfherder JSON artifacts being output by a number of tasks, for example: https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=BUF9J7vZRmOtLdGY1PtX0w.0&revision=230222251c2f6052a17034e45ed6643753580483&searchStr=test-linux2404-64%2Fdebug-mochitest-chrome-1proc-2
|
||
Updated•3 months ago
|
|
Reporter | |
Comment 1•3 months ago
|
||
:bhearsum, I see you added these in bug 2002681. Could you take a look at this? It looks like there's an artifact being outupt in the build/ and test/ folder which is causing this issue since they're the exact same data.
|
||
Comment 2•3 months ago
|
||
So this is happening because we upload /builds/worker/artifacts to two separate artifact locations:
public/build:
expires: '2026-05-25T11:37:12.745Z'
path: /builds/worker/artifacts/
type: directory
public/test:
expires: '2026-05-25T11:37:12.745Z'
path: /builds/worker/artifacts/
type: directory
It's unclear to me why or how this is happening. It looks like it might be exclusive to the 24.04 jobs, as I don't see it in a 22.04 job from the same push: https://firefox-ci-tc.services.mozilla.com/tasks/cIP3OihlTlaXWLCj5U5yfQ
The real problem IMO is the double uploading of artifacts, which is undesirable for other reasons as well.
Description
•