Releases/Firefox 3.0.1:BuildNotes
< Releases
Jump to navigation
Jump to search
Build Engineers
bhearsum
Version/config bump bug
Bonsai queries
Updated CVS Tags devmo page.
Tags
Build 1:
| Module | Branch | Tag | Pull date |
| cvsroot/mozilla | HEAD | FIREFOX_3_0_1_BUILD1 | 2008-07-02 01:52 PDT |
| l10n/l10n | HEAD | FIREFOX_3_0_1_BUILD1 | 2008-07-02 01:52 PDT |
Build data
| Type | Build ID | SHA1 | Push date | Build machine |
| [Windows installer/zip] | fx-win32-1.9-slave2 | |||
| [Mac compressed] | fx-mac-1.9-slave2 | |||
| [Linux compressed] | fx-linux-1.9-slave2 |
Notes
Build 1
Bootstrap Tag: RELEASE_AUTOMATION_M10
Setup before starting:
- Updated master.cfg, bootstrap.cfg. Retagged bootstrap.cfg.
- On the slaves:
- verify that linux has 'DISPLAY=:0 xhost +' set
- remove /builds/verify/firefox-3.0rc3 and firefox-3.0rc2
- update tinderbox to RELEASE_AUTOMATION_M10
- For win32:
cd /e/builds/tinderbox/mozilla/tools/tinderbox
cvs up -r RELEASE_AUTOMATION_M9_1
for dir in fx19rel fx19l10nrel xr19rel; do
cd /e/$dir;
for f in `ls *.pl *.html INSTALL README | grep -v tinder-config.pl`; do
cp -pv /e/builds/tinderbox/mozilla/tools/tinderbox/$f .;
done
cp -pv post-mozilla-rel.pl post-mozilla.pl
done
- On the linux slave, removed:
- /builds/updates/firefox-3.0rc3
- /builds/source/*
- /data/cltbld/firefox-3.0rc3
- For some reason bm-xserve11 was attached to the buildbot master.
- Disconnected it, and reconnected the proper slave (bm-xserve10/fx-mac-1.9-slave2
- Space on slaves before starting:
- fx-linux-1.9-slave2: 29G on /builds
- fx-mac-1.9-slave2: 24G on /
- fx-win32-1.9-slave2: 17G on d:, 2G on e: (disk heavy work is done on d, eg update_verify. build/repack is done on e, but mostly just overwrites existing data)
- Disabled everything after Updates::Push in master.cfg (local modification) because additional patcherconfig/update work needs to be done after Updates::execute but
before updates::push.
- Gulped, and kicked off automation:
buildbot sendchange --username=bhearsum --master=localhost:9989 -m"Firefox 3.0.1build1 release" gogogo
Tag
Automated, no problems.
Source
Automated, no problems
Build
- TinderConfig failed with:
Step TinderConfig died: ASSERT: no replacement found for appVersion at Bootstrap/Config.pm line 364, <INFILE> line 287.
Not sure why this happened ('version' should be used when appVersion isn't present, I think. Maybe it's not when oldAppVersion is present?). Added it to the config, checked in, tagged, restarted builds.
- TinderConfig failed spuriously because en-US configs were already tagged. Commented out TinderConfig from master.cfg and restarted builds.
- Build failed out on Mac - /usr/bin/python was pointing to python2.3 - repointed it to /tools/python/bin/python (python 2.5). not sure how this happened, or how it worked for 3.0rc1/2/3. maybe related to above comments about bm-xserve11.
- Build failed out on win32 due to disk space. Deleted some trees on e: and restarted. (10G free @ time of restart)
Repack
- Mac repack was done incorrectly because of the TinderConfig problem mentioned above. Only the en-US tinder-config for mac and win32 was bumped. TinderConfig was manually re-run on win32 and mac. This was done before win32 started repacking (therefore, it did the right thing the first time), but after mac had completed its full repack. All of the mac repacks were deleted from stage, and Repack::Excute and ::Push were re-run. This produced the correct builds.
- No other problems
Sign
L10nVerify
No changes
Generate Updates
- Ran PatcherConfig & Updates::Execute to get Mac snippets.
- Didn't get a 'aus2.beta' directory (beta + release channel snippets were in the same directory).
- Fixed that by adding 'beta-dir' to <current-update> stanza in the patcher config
- Re-ran Updates::Execute - got aus2.beta this time
- Did a spot check, things looked OK.
- Updated patcher config to get linux & win32 partials/snippets (from: 3.0rc2, to: 3.0.1, comment out rc3 release stanza, comment out mac from rc2, comment out 3.0rc2 to 3.0rc3 past-update line)
- Commented out 'clean update area' so we don't clobber the mac snippets.
- backup mac snippets:
cp -R 3.0rc3-3.0.1/ 3.0rc3-3.0.1.rc3.mac cp -R 3.0.rc3-3.0.1/ ~/3.0rc3-3.0.1.rc3.mac
- Re-ran Updates::Execute to generate linux and win32 partials/snippets
- Got the following at the bottom of the log:
Can't stat /builds/updates/firefox-3.0.1/patcher/temp/firefox/3.0rc3-3.0.1/aus2.test: No such file or directory at Bootstrap/Step/Updates.pm line 110
Can't stat /builds/updates/firefox-3.0.1/patcher/temp/firefox/3.0rc3-3.0.1/aus2: No such file or directory
at Bootstrap/Step/Updates.pm line 119
- This is because we're generating snippets for a release that is NOT the 'version' as set in bootstrap.cfg. Manual spotcheck below to make sure everything is ok.
- Manual spotchecks:
# in aus2.test: look for non-test channels snippets in test channel dir find . -mindepth 6 -type d | grep -v test # expect no output # the same thing for beta, and release channel # in aus2.beta find . -mindepth 6 -type d | grep -v beta # expect no output # in aus2 find . -mindepth 6 -type d | grep -v release # expect no output
- Inspected a few snippets from various places - they look OK.