Closed Bug 1515649 Opened 5 years ago Closed 5 years ago

Windows 2012 AArch64 Bustages unable to open z:\build\build\src\browser/config/mozconfigs/win64-aarch64/beta: when Gecko 66 merges to Beta on 2019-01-21

Categories

(Release Engineering :: Release Automation: Other, defect)

defect
Not set
normal

Tracking

(firefox-esr60 unaffected, firefox64 unaffected, firefox65 unaffected, firefox66+ verified)

VERIFIED FIXED
Tracking Status
firefox-esr60 --- unaffected
firefox64 --- unaffected
firefox65 --- unaffected
firefox66 + verified

People

(Reporter: CosminS, Unassigned)

Details

Attachments

(3 files)

[Tracking Requested - why for this release]:

Central as beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception&revision=f220b8a98eed05949b556b11fcfdc244cb83c0a9&selectedJob=218121299&searchStr=windows%2C2012%2Caarch64%2Copt%2Cbuild-win64-aarch64-msvc-nightly%2Fopt%2C%28n%29

Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=218121299&repo=try&lineNumber=665

13:50:56     INFO - [mozharness: 2018-12-20 13:50:56.590000Z] Skipping clobber step.
13:50:56     INFO - [mozharness: 2018-12-20 13:50:56.590000Z] Running build step.
13:50:56     INFO - Running main action method: build
13:50:56     INFO - Use mozconfig: z:\build\build\src\browser/config/mozconfigs/win64-aarch64/beta
13:50:56     INFO - Reading from file z:\build\build\src\browser/config/mozconfigs/win64-aarch64/beta
13:50:56    FATAL - unable to open z:\build\build\src\browser/config/mozconfigs/win64-aarch64/beta: No such file or directory
13:50:56    FATAL - Running post_fatal callback...
13:50:56    ERROR - setting return code to 2 because fatal was called
13:50:56  WARNING - setting return code to 2
13:50:56    FATAL - Exiting -1

This looks to be a regression from Bug 1514407. Tom please take a look at this. Thank you.
Flags: needinfo?(mozilla)
The optimization doesn't actually do what it claims. For the optimization to be
considered, a task needs to be in the target graph, but then all the
dependencies will be too, which inhibits this optimization.
We want these tasks to run if-and-only if the corresponding build does.
Now that the upload-* kinds inherit `run-on-projects`, we don't need to special
case handling of them in target-tasks.
Flags: needinfo?(mozilla)
Failures no longer appear in beta-simulations when importing the patches. Should we land them on autoland?
Flags: needinfo?(mozilla)
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/82a275a5097f
[taskgraph] Remove `only-if-dependencies-run` optimization; r=dustin
https://hg.mozilla.org/integration/autoland/rev/90124cc372c5
[taskgraph] Inherit run-on-projects for upload-* kinds; r=dustin
https://hg.mozilla.org/integration/autoland/rev/9cb78d2e31fb
[taskgraph] Disable asan-reporter-nigthly via run-on-projects; r=dustin
Flags: needinfo?(mozilla)
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/4dac195e120e
Port bug 1515649 - [taskgraph] Remove only-if-dependencies-run optimization. rs=bustage-fix DONTBUILD
Pushed by thunderbird@calypsoblue.org:
https://hg.mozilla.org/comm-central/rev/7950e082870e
Port bug 1515649 - [taskgraph] Remove only-if-dependencies-run optimization, take 2. rs=bustage-fix r=rjl
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: