Closed
Bug 1865299
Opened 6 months ago
Closed 6 months ago
Artifact builds can't find artifacts when git-cinnabar knows of local commits unknown to mozilla-central/autoland
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(firefox122 fixed)
RESOLVED
FIXED
122 Branch
Tracking | Status | |
---|---|---|
firefox122 | --- | fixed |
People
(Reporter: glandium, Assigned: glandium)
Details
Attachments
(1 file)
It fails with this message:
Exception: Could not find any candidate pushheads in the last 50 revisions.
Search started with e664fbc3ec002ca7497b35362146728122477413, which must be known to Mozilla automation.
e664fbc3ec002ca7497b35362146728122477413 is a changeset unknown to Mozilla automation, but its parent is known. It comes from some fancy stuff I did locally, but it could just as well come from git cinnabar fetch
'ing from try, which would be a more common way to end up in this situation.
Assignee | ||
Comment 1•6 months ago
|
||
_get_recent_public_revisions is not reliably giving us revisions that
are available on the trees that artifacts are taken from. With both
mercurial and git, it is possible to end up in a situation where the
first few entries are only available on some private branch (but still
"public" in mercurial's or git-cinnabar's eye).
In that case, try parent revisions.
Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/c1d659062167 Try harder to find candidate pushheads. r=firefox-build-system-reviewers,sergesanspaille
Comment 3•6 months ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 months ago
status-firefox122:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•