Closed Bug 1184085 Opened 6 years ago Closed 6 years ago

L10N nightly repacks should use compiler from tooltool

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(firefox42 fixed)

RESOLVED FIXED
Tracking Status
firefox42 --- fixed

People

(Reporter: rail, Assigned: rail)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

Just realized that even l10n repacks download gcc from tooltool, but still use the one from /tools. Changing the mozconfigs should fix this.
Our release scripts try to use the following tooltool manifest:

command: START
command: sh ../scripts/scripts/tooltool/tooltool_wrapper.sh browser/config/tooltool-manifests/linux32/l10n.manifest http://tooltool.pvt.build.mozilla.org/build setup.sh /builds/tooltool.py
command: cwd: mozilla-beta
command: output:
browser/config/tooltool-manifests/linux32/l10n.manifest doesn't exist, skipping...
command: END (0.00s elapsed)

Maybe we should use the same manifest with nightly builds. It contains the scache tarball, but it's easier to keep them in sync this way.
Looks like we never used these l10n-specific tooltool manifests - they don't exist. Let's get rid of those and use the same manifests with nightlies. It doesn't mean that we are going to use all of tools from them, that part is controlled by mozconfigs. This will allow nightly l10n repacks (and release promotion repacks using the same script) using tooltool gcc and avoid installing a bunch of gcc rpm packages.
Attachment #8634062 - Flags: review?(bhearsum)
Attachment #8634063 - Flags: review?(bhearsum)
Component: Mozharness → General Automation
QA Contact: jlund → catlee
After the buildbot patches are in production, we can land this one.
Attachment #8634071 - Flags: review?(bhearsum)
Attachment #8634062 - Flags: review?(bhearsum) → review+
Attachment #8634063 - Flags: review?(bhearsum) → review+
Attachment #8634071 - Flags: review?(bhearsum) → review+
https://hg.mozilla.org/mozilla-central/rev/cf83f0b6a920
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
It worked fine:

05:01:23     INFO -   0:05.17 checking for objcopy... /builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/objcopy
05:01:23     INFO -   0:05.18 checking for gcc... /builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/gcc -m32 -march=pentiumpro
05:01:23     INFO -   0:05.20 checking whether the C compiler (/builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/gcc -m32 -march=pentiumpro  ) works... yes
05:01:23     INFO -   0:05.20 checking whether the C compiler (/builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/gcc -m32 -march=pentiumpro  ) is a cross-compiler... no
05:01:23     INFO -   0:05.21 checking whether we are using GNU C... yes
05:01:23     INFO -   0:05.23 checking whether /builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/gcc -m32 -march=pentiumpro accepts -g... yes
05:01:23     INFO -   0:05.23 checking for c++... /builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/g++ -m32 -march=pentiumpro
05:01:23     INFO -   0:05.26 checking whether the C++ compiler (/builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/g++ -m32 -march=pentiumpro  ) works... yes
05:01:23     INFO -   0:05.26 checking whether the C++ compiler (/builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/g++ -m32 -march=pentiumpro  ) is a cross-compiler... no
05:01:23     INFO -   0:05.27 checking whether we are using GNU C++... yes
05:01:23     INFO -   0:05.28 checking whether /builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/g++ -m32 -march=pentiumpro accepts -g... yes
05:01:23     INFO -   0:05.31 checking for ranlib... ranlib
05:01:23     INFO -   0:05.31 checking for as... /builds/slave/m-cen-lx-l10n-ntly-1-000000000/build/mozilla-central/gcc/bin/as
Blocks: 902876
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.