436349 - set up SeaMonkey Mac unit/mochi/crash/reftest buildbot slave

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect)

Description

[Robert Kaiser]

bug 431451 gave us a machine for the Mac unit test slave, I'm doing the setup - most of which is actually done by now.

Comment 1

[Robert Kaiser]

After some slight config changes, see http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=mozilla%2Ftools%2Fbuildbot-configs%2Ftesting%2Fseamonkey&file=&filetype=match&who=kairo%25kairo.at&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-05-29&maxdate=2008-05-31&cvsroot=%2Fcvsroot I could get the Mac slave to run all tests.

It's still hidden from the main SeaMonkey waterfall page (use http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&noignore=1 to see its column) due to its being orange, caused by some test failures:

9 unit tests fail, from what I see all in abook, Mark says they are because of us not supporting OSX abook integration yet.

7 mochichrome tests fail, all being autocomplete tests, not sure what causes that yet.

Comment 2

[Mark Banner (:standard8)]

(In reply to comment #1)
> 7 mochichrome tests fail, all being autocomplete tests, not sure what causes
> that yet.

I just tried this out. A current SeaMonkey trunk build (unmodified) did fail in the same way. So I then built a SeaMonkey trunk with MOZ_PLACES defined, xpfe/components/autocomplete disabled and the elif removed from xul.css. With that build the autocomplete tests all passed.

Comment 3

[Robert Kaiser]

Mark discovered that bug 231754 apparently was toolkit-only, so those autocomplete tests probably fail on Mac because of this.

Comment 4

[Robert Kaiser]

With a checking for bug 436794 today, there's no explicitely failing tests on this box now, I turned it visible on the tinderbox waterfall right before the switch to comm-central. Let's call it done