http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1296832698.1296835784.16899.gz Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test mochitest-other on 2011/02/04 07:18:18 s: talos-r3-snow-009 mochitest-browser-chrome time out running browser_tabview_bug625424.js, which doesn't have a history of timing out, then http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1296840207.1296843348.16217.gz Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test mochitest-other on 2011/02/04 09:23:27 s: talos-r3-snow-009 mochitest-browser-chrome time out running browser_settitle.js, which doesn't have a history of timing out, followed by either more failures or fallout from that timeout. I retriggered both of those runs, hoping to get one of them to catch a different slave, and if I could sit and watch the tree I'd call that good enough, but today's not going to give me much time for anything.
Renamed buildbot.tac to buildbot.tac.bug631587, stopped buildbot.
Assignee: nobody → coop
Status: NEW → ASSIGNED
Priority: -- → P2
The wireless network selection dialog had popped up. I cancelled out of it, turned off Airport, renamed buildbot.tac, and then rebooted the box.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
I believe the wireless that popped up normally comes up when you let the machine sitting for a while. With that I mean that might have not been related but it popped up for standing waiting. NOTE: This is a theory from previous interactions with snow machines but I don't have data to back it up. Nevertheless there is bug 628744 to fix it.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.