Automatically determine "base revision" hashes during |mach artifact|
Categories
(Firefox Build System :: Mach Core, enhancement, P3)
Tracking
(firefox85 affected)
Tracking | Status | |
---|---|---|
firefox85 | --- | affected |
People
(Reporter: mhentges, Assigned: glandium, NeedInfo)
References
Details
(Keywords: in-triage)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
As noted by bugs like 1676107, sometimes there's dirty files in-tree but it's not obvious to developers why that's causing mach artifact
to fail.
As discussed in the most-recent build peers meeting, when calculating artifact hashes, we should use the state of input files as they are on the current "base revision", rather than the current state on the file system.
Comment 1•4 years ago
|
||
Random thought: you may want to list the outgoing/changed files and only consult the VCS for THOSE files, and keep the existing logic for the unchanged files. Otherwise it's probably going to be prohibitively slow with Mercurial.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
This enables mach artifact
and mach bootstrap
to not fail due to local changes.
Comment 4•4 years ago
|
||
bugherder |
Comment 5•4 years ago
|
||
Backed out on request: https://hg.mozilla.org/integration/autoland/rev/739b53fbd7214daa7c71e79c95705189c666a674
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Comment 8•4 years ago
|
||
bugherder |
Comment 9•4 years ago
|
||
Backed out as requested: https://hg.mozilla.org/integration/autoland/rev/f4001dfef5bc1a5407956173bba6aff1ebce1760
Assignee | ||
Comment 10•4 years ago
|
||
It broke pushing changes to toolchain scripts to try: no toolchain builds are triggered by the decision task.
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Backout merged: https://hg.mozilla.org/mozilla-central/rev/f4001dfef5bc
Comment 12•4 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:glandium, could you have a look please?
For more information, please visit auto_nag documentation.
Description
•