Closed Bug 390519 Opened 13 years ago Closed 12 years ago

Create "production" mac buildbot slave for TRUNK

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Unassigned)

References

Details

We already have staging buildbot slave (bm-xserve14). We also need an identical buildbot slave for production pool...
Assignee: build → joduinn
Priority: -- → P2
bm-xserve12.build.mozilla.org has been reimaged and is now ready for buildbot slave to be installed.
Status: NEW → ASSIGNED
The buildbot slave "macosx-slave2" is now installed in the cltbld account, and seems to be working fine.

While waiting for build-console.build.mozilla.org to be setup, I wanted to sanity check that this new slave works correctly. So, I've temporarily added macosx-slave2 to the existing staging-build-console buildmaster, and triggered a build. This same step worked fine with buildbot slave macosx-slave1, so should work equally well with this new macosx-slave2.

macosx-slave2 starts ok, but the tinder-config step within the macosx-build failed with the following error:


perl ./release -o TinderConfig
 in dir /Users/cltbld/macosx-slave2/macosx_build/build (timeout 36000 secs)
 watching logfiles {}
 argv: ['perl', './release', '-o', 'TinderConfig']
 environment: {'TERM': 'xterm-color', 'SHELL': '/bin/bash', 'MAIL': '/var/mail/cltbld', 'SHLVL': '1', 'PYTHONPATH': '/tools/buildbot/lib/python2.5/site-packages:/tools/twisted/lib/python2.5/site-packages:/tools/twisted-core/lib/python2.5/site-packages/:/tools/zope-interface/lib/python2.5/site-packages/', 'OLDPWD': '/Users/cltbld', 'SSH_CLIENT': '10.2.72.11 50159 22', 'TBOX_CLIENT_CVS_DIR': '/builds/tinderbox/mozilla/tools', 'PWD': '/Users/cltbld/macosx-slave2', 'CVS_RSH': 'ssh', 'PYTHONHOME': '/tools/python', 'USER': 'cltbld', 'SSH_TTY': '/dev/ttyp1', 'PATH': '/tools/buildbot/bin:/tools/twisted/bin:/tools/twisted-core/bin:/tools/python/bin:/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin', 'LOGNAME': 'cltbld', 'SSH_CONNECTION': '10.2.72.11 50159 10.2.71.12 22', 'HOME': '/Users/cltbld', '_': '/tools/buildbot/bin/buildbot'}
Can't locate Config/General.pm in @INC (@INC contains: /System/Library/Perl/5.8.6/darwin-thread-multi-2level /System/Library/Perl/5.8.6 /Library/Perl/5.8.6/darwin-thread-multi-2level /Library/Perl/5.8.6 /Library/Perl /Network/Library/Perl/5.8.6/darwin-thread-multi-2level /Network/Library/Perl/5.8.6 /Network/Library/Perl /System/Library/Perl/Extras/5.8.6/darwin-thread-multi-2level /System/Library/Perl/Extras/5.8.6 /Library/Perl/5.8.1 .) at Bootstrap/Step/PatcherConfig.pm line 7.
BEGIN failed--compilation aborted at Bootstrap/Step/PatcherConfig.pm line 7.
Compilation failed in require at ./release line 13.
BEGIN failed--compilation aborted at ./release line 13.
program finished with exit code 2

For now, I've put back staging-build-console to use the previous macosx-slave1, which works, so that end-to-end runs continue to work, while we debug.
Blocks: end2end-bld
Hardware: PC → Macintosh
Turns out our instructions were missing a step. Added instructions for missing Config::General at: 
http://wiki.mozilla.org/ReferencePlatforms/BuildBot#Install_python
..which fixed this.

Note: because this machine (bm-xserve12) is Intel based, not PowerPC, we cannot use it for the Mozilla1.8 / FF2.0.0.x branch. However, we can use this for TRUNK / FF3.x branch, so updating summary accordingly.
Summary: Create mac buildbot slave → Create "staging" mac buildbot slave for TRUNK
Summary: Create "staging" mac buildbot slave for TRUNK → Create "production" mac buildbot slave for TRUNK
Priority: P2 → P3
Priority: P3 → P2
Slave is still running ok. However, need buildmaster to handle TRUNK in addition to the 1.8 branch before we can close this bug. 

Havent been able to work on this recently, so putting this back in the pool for now.
Assignee: joduinn → build
Status: ASSIGNED → NEW
OS: Mac OS X → All
Priority: P2 → P3
Hardware: Macintosh → All
Assignee: build → nobody
QA Contact: mozpreed → build
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.