Closed Bug 536170 Opened 15 years ago Closed 15 years ago

moz2-win32-slave01 and 35 were hung in a weird state

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 522078

People

(Reporter: armenzg, Unassigned)

Details

(Whiteboard: [buildduty])

Attachments

(1 file)

Slaves win32-slave{01,35} were in a weird state when I started my day. I VNCed into them and they had a gray screen that as soon as I logged into them it started loading personal settings and just going ahead as it should have done without me having to log in. A couple of mins later, after having logged in, nagios mentions that the slaves are good again. NOTE: From scrolling back I can see that win32-slave13 had been on that state as well but 5 minutes later it was OK. http://production-master.build.mozilla.org:8010/buildslaves/win32-slave01 http://production-master.build.mozilla.org:8010/buildslaves/win32-slave35
Whiteboard: [buildduty]
Summary: moz2-win32-slaveXX.build:buildbot is CRITICAL: CRITICAL: python.exe: stopped (critical) → moz2-win32-slave01 and 35 were hung in a weird state
Attached image [screenshot]
These slaves were in the same state: win32-slave30 win32-slave37 try-w32-slave18 try-w32-slave19 All I had to do is to VNC to the slave.
This is the same thing Nick mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=522078#c25. Duping over to that.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: