Closed
Bug 594770
Opened 15 years ago
Closed 15 years ago
Most XP rev3 minis were stuck in the screen saver
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: armenzg)
Details
(Whiteboard: [buildduty][talos])
From looking at the slaves one of the last jobs it did was on Sep 6th around noon which kind of points to the outage on Monday.
There only few slaves that were still up and running.
The problem I noticed was when I VNCed into the machine it would be running the screen saver, after clicking twice it would start "Loading your personal settings" and start the buildbot scripts.
Some of these slaves (14,16,18,32,34,42,43,45,46,47,48,49,50,51,52) had an OPSI screen (sometimes behind the screen saver) saying that could not connect. I had to discard three messages and it would eventually login.
I have kicked slaves 10 and on leaving behing the first 6 in the state that I have found them this morning.
The states of the slaves could have been infered from looking at the testpool waitimes (XP had 16% this morning) and/or from the inactive talos emails.
John could you have a look at the list of connected XP slaves at the EOD? They should not go down again from what I understand.
Updated•15 years ago
|
OS: Mac OS X → Windows XP
Priority: -- → P3
Whiteboard: [buildduty]
Updated•15 years ago
|
Whiteboard: [buildduty] → [buildduty][talos]
| Assignee | ||
Comment 1•15 years ago
|
||
I fixed this some time ago but forgot that I had actually filed a bug.
Assignee: nobody → armenzg
Status: NEW → RESOLVED
Closed: 15 years ago
Priority: P3 → P2
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•