L10n jobs are missing the setup stub - nightlies end up in exception
Categories
(Release Engineering :: Release Automation, defect)
Tracking
(firefox67 fixed)
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: CosminS, Unassigned)
References
Details
Attachments
(2 files)
Th push with exceptions: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&resultStatus=exception&revision=815f7149b30b27f79395d9a0155c1ebeb4fca8b5&selectedJob=224710490
https://taskcluster-artifacts.net/DpRFKOWnSIWqM2zVuYzYGw/1/public/logs/chain_of_trust.log
Callek said he will try to bisect this.
Pushlog from the latest green nightly to the exceptions: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d305772af471&tochange=815f7149b30b
Comment 1•6 years ago
|
||
My current theory is Bug 1522354 - nalexander asked me to n-i him to get it in a queue -- I have a try push of a backout to test the theory: https://treeherder.mozilla.org/#/jobs?repo=try&revision=58aa8a88b7ab388bab1b1c59a0ca1c1e81cb3416
Comment 2•6 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #1)
My current theory is Bug 1522354 - nalexander asked me to n-i him to get it in a queue -- I have a try push of a backout to test the theory: https://treeherder.mozilla.org/#/jobs?repo=try&revision=58aa8a88b7ab388bab1b1c59a0ca1c1e81cb3416
I don't understand why this line is present, but it smells bad:
if test "$OS_ARCH" = "WINNT"; then
if ! test "$HAVE_64BIT_BUILD"; then
if test "$MOZ_UPDATE_CHANNEL" = "nightly" -o \
"$MOZ_UPDATE_CHANNEL" = "nightly-try" -o \
"$MOZ_UPDATE_CHANNEL" = "aurora" -o \
"$MOZ_UPDATE_CHANNEL" = "beta" -o \
"$MOZ_UPDATE_CHANNEL" = "release"; then
if ! test "$MOZ_DEBUG"; then
if ! test "$USE_STUB_INSTALLER"; then
# Expect USE_STUB_INSTALLER from taskcluster for downstream task consistency
echo "ERROR: STUB installer expected to be enabled but"
echo "ERROR: USE_STUB_INSTALLER is not specified in the environment"
exit 1
fi
MOZ_STUB_INSTALLER=1
fi
fi
fi
fi
It's ancient -- one wonders what's actually supposed to happen here now? Callek, can you try dropping it?
Comment 3•6 years ago
|
||
In Bug 1522354, the default for --host was changed to detect running on a 64bit host.
Since --target defaults to --host, this changed the default for --target
as well. This didn't affect builds, as they explictly set the --target in
build/win32/mozconfig.vs2017. Set it explicitly in L10n builds as well.
Comment 5•6 years ago
|
||
| bugherder | ||
Comment 6•6 years ago
|
||
This was 1522354 for sure, my try push proved that -- Thanks Tom for writing the patch.
I'm leaving my n-i open so I can fix the devedition mozconfig tomorrow though (otherwise we'll hit this on next staging build/uplift)
| Comment hidden (Intermittent Failures Robot) |
Comment 8•6 years ago
|
||
In Bug 1522354, the default for --host was changed to detect running on a 64bit host. Since --target
defaults to --host, this changed the default for --target as well. This didn't affect builds, as they
explictly set the --target in build/win32/mozconfig.vs2017. Set it explicitly in L10n builds as well.
This patch also fixes devedition
Updated•6 years ago
|
| Comment hidden (Intermittent Failures Robot) |
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
| bugherder | ||
Updated•1 year ago
|
Description
•