Closed
Bug 1406346
Opened 7 years ago
Closed 6 years ago
Local changes should not break the capability to install binaries from tc
Categories
(Firefox Build System :: General, defect, P4)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Sylvestre, Assigned: Sylvestre)
References
Details
Attachments
(1 file)
$ echo "" >> build/build-clang/build-clang.py
$ hg commit -m "test" build/build-clang/build-clang.py
$ ./mach static-analysis install
Could not find artifacts for a toolchain build named `linux64-clang-tidy`
Best case scenario, "./mach static-analysis install" will still work
Worst case scenario, we should have an error message like 'your local repository (changeset "foo") differs from the one expected (changeset "bar") or you have some artifact in your directory.'
Assignee | ||
Updated•7 years ago
|
status-firefox58:
affected → ---
Comment 1•7 years ago
|
||
The artifact identifiers are based on a hash of file inputs. So if you change an input file...
To make this "just work" (which would violate a constraint that used artifacts are based on hash of inputs), we'd have to read the old versions of files from version control. And to detect local changes, we'd also have to query for "local commits." That is achievable in Mercurial via phases. Git is a bit harder because identifying refs is a bit involved.
Either way, we would need to more tightly integrate VCS into the artifacts code. This is a... sensitive topic.
Anyway, the error message isn't a lie. There is certainly room to improve it though. But it feels low priority.
Priority: -- → P4
Assignee | ||
Comment 2•7 years ago
|
||
I don't think it is a low priority.
For none-specialist of that stuff, this is frustrating.
Works in a clean tree, as soon as you touch a file, it is not working anymore without any clear reason (it is not obvious that it is based on a hash of the local files).
At least, we should have a better error message.
Keywords: leave-open
Comment hidden (mozreview-request) |
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8925478 [details]
Bug 1406346 - In case of error, tell to the dev that it might be caused by temporary files
https://reviewboard.mozilla.org/r/196604/#review205014
I don't think this error message is very helpful.
How about something like: "Local commits and other changes in your checkout may cause this error. Try updating to a fresh checkout of mozilla-central to use artifact builds."
Attachment #8925478 -
Flags: review?(gps) → review-
Comment 5•7 years ago
|
||
I wonder if it should be a good idea that in the message to also include the paths where potential issues might occur, or maybe if we extend this further do a:
>>hg status
And with the result of the of the hg command match it against our list of paths that are part of the hash? What do you think about this?
Flags: needinfo?(gps)
Comment 6•7 years ago
|
||
The user may not be using mercurial, and the changes may well be committed.
Comment hidden (mozreview-request) |
Comment 8•7 years ago
|
||
mozreview-review |
Comment on attachment 8925478 [details]
Bug 1406346 - In case of error, tell to the dev that it might be caused by temporary files
https://reviewboard.mozilla.org/r/196604/#review206512
Attachment #8925478 -
Flags: review?(gps) → review+
Pushed by gszorc@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/82ea4b82a7fa
In case of error, tell to the dev that it might be caused by temporary files r=gps
Comment 10•7 years ago
|
||
There is definitely room to improve the detection. IMO the build system should consider rejecting artifact builds if certain files have been changed locally.
ahal recently added a `base_ref` property to mozversioncontrol. With that, it should be possible to collect the set of changed paths between base and current. And with that, we can start building in some more intelligent smarts here.
Flags: needinfo?(gps)
Comment 11•7 years ago
|
||
This is *not* about artifact builds.
Comment 12•7 years ago
|
||
bugherder |
Updated•7 years ago
|
Product: Core → Firefox Build System
Comment 13•6 years ago
|
||
The leave-open keyword is there and there is no activity for 6 months.
:kmoir, maybe it's time to close this bug?
Flags: needinfo?(kmoir)
Comment 14•6 years ago
|
||
:sylvestre is this still an issue for you or can the bug be closed?
Flags: needinfo?(kmoir) → needinfo?(sledru)
Updated•6 years ago
|
Flags: needinfo?(kmoir)
Assignee | ||
Comment 15•6 years ago
|
||
This isn't perfect but good enough.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(sledru)
Keywords: leave-open
Resolution: --- → FIXED
Updated•6 years ago
|
Flags: needinfo?(kmoir)
Updated•6 years ago
|
Assignee: nobody → sledru
You need to log in
before you can comment on or make changes to this bug.
Description
•