User:Bhearsum:3.1b3 Testrun 1

From MozillaWiki
Jump to navigation Jump to search

Notes

Because of bug 466222 releases/mozilla-1.9.1 cannot be cloned to users/stage-ffxbld/mozilla-1.9.1. To work around this, it was cloned manually to users/stage-ffxbld/mozilla191 and release_config.py was adjusted accordingly. This isn't a problem in production since we don't need to clone the production repositories.

Also because of this the dependent schedulers will not work, because repo_setup appears to fail. Builders were kicked along manually for this test run with 'Force Build'.

Setup

  • Applied patches in bug 470966
  • Updated l10n-changesets locally on staging-master:
hg clone http://hg.mozilla.org/build/tools
cd tools/release
bash get-l10n-revs af ar be bg bn-IN ca cs cy de el en-GB eo es-AR es-ES et eu fi fr fy-NL ga-IE gu-IN he hi-IN hu id is it ja ja-JP-mac ka kn ko lt lv mr nb-NO nl nn-NO pa-IN pl pt-BR pt-PT ro ru si sk sl sq sv-SE te tr uk zh-CN zh-TW
cp l10n-changesets /builds/buildbot/moz2-master
  • Bumped release_config.py to 3.1b3
  • Kicked off automation:
buildbot sendchange --username=bhearsum --master=localhost:9010 --branch=users/stage-ffxbld/mozilla191 -m "Firefox 3.1b3" doit

Tag

  • Tagging failed out because the l10n repositories were being cloned from /releases/l10n-mozilla-1.9.1 instead of users/stage-ffxbld. - being fixed in bug 470966
    • To work around this l10nRepoPath was set to releases/l10n-mozilla-1.9.1 for repo_setup and set to users/stage-ffxbld for tag.
  • Wiped out /builds/moz2_slave/tag/* and restarted the step.
  • Bailed out at mozilla191 because the tools repository was not cloned.
    • Tools should be cloned by MozillaBuildFactory regardless of buildSpace argument FIXME
  • Failed out a few times because l10n-changesets had changesets which were on the 3.1b2 relbranch (because these locales had no commits post-b2).
    • Manually futzed with l10n-changesets to fix this. Not sure how to solve this problem for staging in the future. Maybe get-l10n-revs can pick the latest changeset on 'default'?
    • Not a problem for production because l10n-changesets is hand created by l10n team.

Source

  • Uploading failed because UPLOAD_TO_TMP was set instead of UPLOAD_TO_TEMP - bug 472882

Build

  • Complete MARs were not generated/uploaded bug 472880

Repack

  • Repacks failed to checkout l10n code