Closed Bug 570445 Opened 15 years ago Closed 15 years ago

Something's wrong with the new Mac try slaves

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Assigned: lsblakk)

References

Details

(Whiteboard: [tryserver][buildslaves])

It's not incredibly obvious what's wrong like it would be with things we have tests for, like color depth or screen resolution (at least, I think that has a test), but looking at the 8 mochitest-other runs on the last four try pushes, 3 were green, all on slaves < 20, and five failed in the exact same way, 15 failures in mochitest-chrome, and 4 timeouts resulting in suite failure in mochitest-browser-chrome, all five on slaves >= 20. For mochitest-4, it was 2 green runs, both on try-mac-slave19, and 6 failed runs, all 15 failures (plus on a leak, for the debug runs), all on slaves >= 20.
try-mac-slave20 thru 29 came from bug 568243. They're launching the 'Bluetooth Setup Assitant' on boot because they think the mouse should coming from there. It won't let me disable bluetooth with this message: 'You cannot control your computer if you turn Bluetooth off at this time as you would lose your input devices' Some of these machines have the hostname correct at the prompt but not on the title of the VNC window. Non-obvious how that would screw up tests but something is clearly rotten here. I've disabled buildbot on them and Lukas can debug. Some ideas: regression in the image, wrong image used, different imaging method.
Assignee: nobody → lsblakk
Blocks: 568243
Priority: -- → P2
Whiteboard: [tryserver][buildslaves]
The actual imaging was in bug 568268.
Oh, and try-mac-slave28 is down right now so I couldn't rename buildbot.tac there.
Went through and manually unchecked "open bluetooth setup assistant" on reboot so that it will not longer come up. Apparently this was because of an upgrade to the imaging software that caused the system preference of the ref image not to be set in the image created off it. IT is looking into that and in the meantime have added unchecking this preference from new images. The new try macs have all been updated and put back into the production pool.
Status: NEW → RESOLVED
Closed: 15 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.