Closed
Bug 400313
Opened 17 years ago
Closed 17 years ago
[10.5] Setup 10.5 unit test machine
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: samuel.sidler+old, Assigned: rcampbell)
References
Details
Attachments
(2 files, 2 obsolete files)
1.87 KB,
patch
|
Details | Diff | Splinter Review | |
3.16 KB,
patch
|
Details | Diff | Splinter Review |
Since our testing on 10.5 only covers certain things (like, non-layout things which could change with 10.5), we'd like unit tests run on a 10.5 machine. Filing here, per robcee and requesting blocking1.9 since 10.5 will be a Tier 1 platform (I believe).
Flags: blocking1.9?
Assignee | ||
Updated•17 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [requesting hardware]
Assignee | ||
Comment 2•17 years ago
|
||
There's some work to be done for this as we don't have a standard 'refplatform' image for 10.5, we'd be building this up from scratch. This isn't even well-defined in http://developer.mozilla.org/en/docs/Mac_OS_X_Build_Prerequisites yet. From personal experience, getting a build to work requires some bleeding edge third party packages from fink. macports (which we use for the other refplatforms) have problems with libidl.
The MacPorts libidl issues lasted about a week and were fixed around last Wednesday. We should really be using MacPorts instead of fink.
Assignee | ||
Comment 4•17 years ago
|
||
I agree and was speaking about my own efforts to run builds on my local machine after upgrading to Leopard with an old MacPorts tree. Good to know Ports is covered.
Comment 5•17 years ago
|
||
One thing also to note about 10.5 is that niutil (and all of NetInfo) is gone. Directory Services is replacing it. It's good that everything is in a plist on disk now, but it's bad that they've neglected to document it. I ran into all this when I was setting up my own instance of buildbot (for Adium) this weekend. Ouch. As an example, the steps on http://wiki.mozilla.org/ReferencePlatforms/BuildBot/MacOSX become: # All of this assumes you're acting as root. `sudo -s` to get a root shell. dscl . -create /Users/buildbot dscl . -create /Users/buildbot UniqueID 503 dscl . -create /Users/buildbot PrimaryGroupID 503 dscl . -create /Users/buildbot RealName "Buildbot" dscl . -create /Users/buildbot NFSHomeDirectory "/Users/buildbot" dscl . -create /Users/buildbot UserShell "/bin/bash" dscl . -create /Users/buildbot Password '*' dscl . -create /Groups/buildbot dscl . -create /Groups/buildbot PrimaryGroupID 503 # I heard of someone having Finder crash because of an imported user not having # a realname set, so probably better safe that sorry here. dscl . -create /Groups/buildbot RealName "Buildbot Group" passwd buildbot # AFAIK you have to do this -- it doesn't seem to create it on its own when I # tried `sudo -i -u buildbot`. mkdir /Users/buildbot chown buildbot:buildbot buildbot Can't really recommend any one source for documentation, took me a number of hours to figure out what was needed and what wasn't. Comparing to the pre-installed daemons helped a bit (though I don't quite understand their _ naming convention, I'd suggest ignoring it). Using a machine you don't care about that you can wipe if things get nasty is probably a good idea. I had to edit stuff in /var/db/dslocal twice and /var/db/shadow once after nearly hosing everything.
Assignee | ||
Comment 6•17 years ago
|
||
Thanks for the headsup, Colin. It's not super-critical for the unittest machines to run with the same uid and gid, but we have run into issues on the js testing machines where those values were different. Configuring this machine now.
Assignee: nobody → rcampbell
Status: ASSIGNED → NEW
Priority: P3 → P2
Whiteboard: [requesting hardware] → [configuring]
Assignee | ||
Comment 7•17 years ago
|
||
copied the existing osx steps and added a new builder.
Attachment #295391 -
Flags: review?(ccooper)
Assignee | ||
Comment 8•17 years ago
|
||
missed renaming the variable at initialization
Attachment #295391 -
Attachment is obsolete: true
Attachment #295393 -
Flags: review?(ccooper)
Attachment #295391 -
Flags: review?(ccooper)
Updated•17 years ago
|
Attachment #295393 -
Flags: review?(ccooper) → review+
Assignee | ||
Comment 9•17 years ago
|
||
cvs commit: Examining . Checking in auth.py; /cvsroot/mozilla/tools/buildbot-configs/testing/unittest/auth.py,v <-- auth.py new revision: 1.2; previous revision: 1.1 done Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/unittest/master.cfg,v <-- master.cfg new revision: 1.11; previous revision: 1.10 done
Assignee | ||
Comment 10•17 years ago
|
||
fixed a couple of errors, references to defunct machines and a misnamed centos5 builder.
Attachment #295393 -
Attachment is obsolete: true
Assignee | ||
Comment 11•17 years ago
|
||
cvs commit: Examining . Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/unittest/master.cfg,v <-- master.cfg new revision: 1.12; previous revision: 1.11 done
Assignee | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 12•17 years ago
|
||
some crufty additional machines commented out. This needs to be cleaned up properly.
Assignee | ||
Updated•17 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [configuring] → [waiting on cvs key]
Assignee | ||
Updated•17 years ago
|
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Whiteboard: [waiting on cvs key]
Reporter | ||
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•