Closed
Bug 1418671
Opened 7 years ago
Closed 6 years ago
Failing lint builds - source-test-file-metadata-bugzilla-components
Categories
(Firefox Build System :: General, enhancement)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nataliaCs, Assigned: tomprince)
References
Details
Attachments
(1 file)
Log: https://treeherder.mozilla.org/logviewer.html#?job_id=145775119&repo=autoland Seems that it belongs to this push: https://treeherder.mozilla.org/#/jobs?repo=comm-central&revision=306fff0f8a9d1fe8b7eeafd86c68166d78288767
Reporter | ||
Updated•7 years ago
|
Flags: needinfo?(mozilla)
Comment 1•7 years ago
|
||
This Linting opt source-test-file-metadata-bugzilla-components (Bugzilla) has this failure: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=4f92cfb21a2e8c3a3c2cb31fa065cb318a786df7&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=success&filter-searchStr=Bugzilla&selectedJob=145775119 It complains about a missing bugzilla component on every comm-central file on a mozilla trunk push. Missing Bugzilla component: comm/... The machine ran 2 web platform tests before and before that a comm-* ESlint job: https://tools.taskcluster.net/provisioners/aws-provisioner-v1/worker-types/gecko-t-linux-xlarge/workers/us-west-1/i-0d8a4b8c971388f38 https://tools.taskcluster.net/groups/TBLbZWJCTOa0yYbUlUKmNg/tasks/c6YSkIl-Tn2kFk0WOuV0pw/runs/0 https://treeherder.mozilla.org/#/jobs?repo=comm-central&revision=306fff0f8a9d1fe8b7eeafd86c68166d78288767
Assignee | ||
Updated•7 years ago
|
Keywords: leave-open
Pushed by mozilla@hocat.ca: https://hg.mozilla.org/comm-central/rev/0d601be171e5 Disable linting temporarily due to cache poisoning. r=me
Comment hidden (mozreview-request) |
Assignee | ||
Comment 4•7 years ago
|
||
I've turned off linting jobs on comm-central while a fix is pending.
Flags: needinfo?(mozilla)
Comment hidden (Intermittent Failures Robot) |
Comment 6•7 years ago
|
||
mozreview-review |
Comment on attachment 8929799 [details] Bug 1418671: Use a separate cache for builds that checkout comm-central; https://reviewboard.mozilla.org/r/201028/#review206468 The shared store needs to be on the same volume as the checkouts to ensure things don't get out of sync. If they weren't on the same store, you could end up in a situation where the checkout cache has a changeset that isn't in the store cache. While I think robustcheckout will or could deal with this, it is a bad situation because it requires the working directory to be blown away.
Attachment #8929799 -
Flags: review?(gps) → review-
Assignee | ||
Comment 7•7 years ago
|
||
mozreview-review-reply |
Comment on attachment 8929799 [details] Bug 1418671: Use a separate cache for builds that checkout comm-central; https://reviewboard.mozilla.org/r/201028/#review206468 All the build jobs already don't use the same volume, since they do a checkout in the workspace cache, but still point to the checkout cache for the shared store.
Assignee | ||
Updated•7 years ago
|
Attachment #8929799 -
Flags: review- → review?(gps)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Comment 8•7 years ago
|
||
mozreview-review-reply |
Comment on attachment 8929799 [details] Bug 1418671: Use a separate cache for builds that checkout comm-central; https://reviewboard.mozilla.org/r/201028/#review206468 Then the build tasks are buggy. The reason we aren't bit by this is because we only run a single concurrent task on the build workers. For the workers where we can run multiple tasks concurrently (like decision workers), the checkout is on the same cache as the store. I'm *very* nervous about breaking this standard and mixing and matching checkouts and stores. I may just add a sanity check to run-task that fails the task if cache spanning is detected.
Comment 9•7 years ago
|
||
mozreview-review |
Comment on attachment 8929799 [details] Bug 1418671: Use a separate cache for builds that checkout comm-central; https://reviewboard.mozilla.org/r/201028/#review211244 This still gets an r- from me because of cache spanning. To support comm-central, let's put something in the cache name (not necessarily the filesystem path) to delimit which *scope* caches belong to.
Attachment #8929799 -
Flags: review?(gps) → review-
Assignee | ||
Comment 10•7 years ago
|
||
mozreview-review-reply |
Comment on attachment 8929799 [details] Bug 1418671: Use a separate cache for builds that checkout comm-central; https://reviewboard.mozilla.org/r/201028/#review206468 Thanks for the more detailed explanation.
Comment hidden (mozreview-request) |
Comment 12•6 years ago
|
||
mozreview-review |
Comment on attachment 8929799 [details] Bug 1418671: Use a separate cache for builds that checkout comm-central; https://reviewboard.mozilla.org/r/201028/#review213958
Attachment #8929799 -
Flags: review?(gps) → review+
Comment 13•6 years ago
|
||
Pushed by mozilla@hocat.ca: https://hg.mozilla.org/integration/autoland/rev/d38774aa733f Use a separate cache for builds that checkout comm-central; r=gps
Comment 14•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d38774aa733f
Comment 15•6 years ago
|
||
Pushed by mozilla@hocat.ca: https://hg.mozilla.org/comm-central/rev/5b6d18ff9a4f Re-enable lints; r=me
Assignee | ||
Updated•6 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 16•6 years ago
|
||
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•