Please drive a stake through talos-r3-leopard-049's and 050's hearts

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: philor, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildslaves][buildduty])

(Reporter)

Description

7 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1291871374.1291874550.5209.gz and http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1291866728.1291869808.16496.gz look like either something eating focus, or the resolution's off, or the window's off the side of the monitor, or some such. Other slaves have done fine with the same test suites in between 049's failures, so it's not code.
I gracefully shut this slave down, and disabled its buildslave from starting up again (with or without the slave allocator):

talos-r3-leopard-049:~ cltbld$ mv talos-slave/buildbot.tac{,.off}
talos-r3-leopard-049:~ cltbld$ touch talos-slave/DO_NOT_START

We can diagnose better in the morning.  Thanks for spotting this, philor!
Whiteboard: [buildslaves][buildduty]
It's the bluetooth wizard again, see bug 570843. The VNC hostname could also do with fixing up, see System Prefs > Sharing.

https://wiki.mozilla.org/PostImage
Blocks: 616157
(Reporter)

Updated

7 years ago
Severity: blocker → normal
Gave talos-r3-leopard-050 the same treatment as 049.
Summary: Please drive a stake through talos-r3-leopard-049's heart → Please drive a stake through talos-r3-leopard-049's and 050's hearts
bluetooth off, slaves back in the pool.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.