Releases/Firefox 17.0.9esr/BuildNotes
- who: nthomas
- tracking: bug 915356
Contents
Checklist
Notes
Issue the first - clobberer
Tagging failed, filed bug 914965
Calling clobberer: /tools/python/bin/python /builds/slave/rel-m-esr17-firefox_tag/scripts/scripts/release/../..//clobberer/clobberer.py -s scripts -s buildprops.json http://clobberer.pvt.build.mozilla.org/always_clobber.php release-mozilla-esr17 release-mozilla-esr17-firefox_tag rel-m-esr17-firefox_tag linux-ix-slave02 http://buildbot-master57.srv.releng.use1.mozilla.com:8001/ Checking clobber URL: http://clobberer.pvt.build.mozilla.org/always_clobber.php?master=http%3A%2F%2Fbuildbot-master57.srv.releng.use1.mozilla.com%3A8001%2F&slave=linux-ix-slave02&builddir=rel-m-esr17-firefox_tag&branch=release-mozilla-esr17&buildername=release-mozilla-esr17-firefox_tag Error contacting server program finished with exit code 1 elapsedTime=0.358182
Redid the sendchange:
# buildbot-master81 $ /builds/releaserunner/bin/buildbot sendchange --who lsblakk@mozilla.com --master buildbot-master81.build.mozilla.org:9301 \ --branch releases/mozilla-esr17 -p products:firefox -p script_repo_revision:FIREFOX_17_0_9esr_RELEASE release_build change sent successfully
Chased the problems down to a cached 403 response, redid the sendchange after making sure that had expired. Still failing.
Turned out to be a problem with urllib2.urlopen() not taking a timeout arg until Python 2.6, while the old slaves have 2.5.1 first on the path. Patched and retagged tools, sendchange.
Issue the second - tag-release.py uses with syntax
Tagging failure, bug 915075.
File "/builds/slave/rel-m-esr17-firefox_tag/scripts/scripts/release/../../lib/python/build/l10n.py", line 68 with open(path.join(sourceRepoName, ".mozconfig"), "a") as mozconfig: ^ SyntaxError: invalid syntax
Patched by importing with from __future__, lots of messy landings, retagged tools, sendchange.
Issue the third - wonky mac slave during build
bld-lion-r5-057 hit an error in configure
configure: error: Perl 5.006 or higher is required.
It'd been burning non-release builds too but disabling in slavealloc hadn't stuck yet. Rebuilt job.
Issue the fourth - l10n repack bustage
On linux32 and linux64 tooltool.py is not found at the location used for mock builds on these non-mock slaves
command: START command: scripts/scripts/tooltool/fetch_and_unpack.sh mozilla-esr17/browser/config/tooltool-manifests/linux64/releng.manifest http://runtime-binaries.pvt.build.mozilla.org/tooltool /builds/tooltool.py setup.sh command: cwd: /builds/slave/rel-m-esr17-l64_rpk_9 command: output: Cannot execute /builds/tooltool.py, exiting
Rail symlinked to victory, see bug 915356 comment #1.
On mac and windows, and would also be linux if they'd got that far:
Adding configure options from /builds/slave/rel-m-esr17-osx64_rpk_5/mozilla-esr17/.mozconfig: --with-l10n-base=../../l10n-central --enable-official-branding ... checking for gcc-4.2... /usr/bin/gcc-4.2 checking for g++-4.2... /usr/bin/g++-4.2 configure: error: Invalid value --with-l10n-base, ../../l10n-central doesn't exist *** Fix above errors and then restart with "make -f client.mk build"from this patch removing support for mozconfigs in buildbot-configs, and we bug 852553 never landed on mozilla-esr17.
Restored code paths for old machines + branches, land+tag, rebuilt all jobs --> Green.
Issue the fifth - updates bustage
bug 908024 was also bad about retaining ESR17 support.
perl tools/release/patcher-config-bump.pl -p fire.... Unknown parameter: -SaveSorted => "1" (key: <SaveSorted>) at tools/release/patcher-config-bump.pl line 170 program finished with exit code 255
We have an older version of Config::General on the ESR17 slaves on the on the mock ones.