Leopard Unittests January 14th, 2008
Last week we added a new machine to the Firefox tree: qm-xserve02. Then we quickly disabled it as it was born in a sea of bright, non-deterministic orange. So, right after I post this, I’m going to re-enable it and then head over to #developers to ask around to see if anyone can make sense of the problems. This is a non-standard (i.e., non-refplatform) build as we’re using Leopard (OS X 10.5, aka Darwin 9.1.0) and all that that implies.
The other problem of note is that builds and testruns take a lot longer on this machine. I don’t know if it’s due to slow disk, slow hardware (should be the same as qm-xserve01? I think?) or some other reason (no, Time Machine is not enabled), but it’s going to cause problems if we have to wait on it to turn green.
So, I’m looking for help with these issues. Feel free to comment here or give me a poke on irc.
Posted in Infrastructure, Mozilla, Testing | Comments (2)
January 14th, 2008 at 2:19 pm
This is a brand new box, should be quicker than 01!
January 14th, 2008 at 2:24 pm
yeah, that was my gut feeling as well. So either the OS is just that much slower (which I’m not noticing locally) or I have some configuration issue. I’ll have to spend some time playing with it.