427723 - I killed the Windows tinderboxen, plz to be fixing my mistake

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Jeff Walden [:Waldo]]

I checked in a patch for bug 418009 which works on OS X and Linux; it also changed some Windows code, and it did so incorrectly.  I just checked in what should be a fix for the problem, but from MozillaTest log examination it seems the boxes that use automation.py.in (those using runtests.py, plus those doing profile-guided optimization on Windows) are now wedged and can't be kicked using the admin interface:

http://mxr-stage.mozilla.org/mozilla/search?string=profileserver&find=&findi=&filter=&hitlimit=&tree=mozilla

So far we're only looking at unittest-stage, the bm-pgo box that was on front page but got dropped back, and the tinderbox link -- which *is* on front page and definitely seems to have hung fx-win32-tbox (and I guess from there is hanging everything waiting on its results).


What needs to be done:
- unwedge fx-win32-tbox on the Firefox tinderbox, probably by manually logging on
  and killing processes

Brownie points if you can do the same on qm-stage-win2k3-01, qm-win2k3-03, and qm-win2k3-02 on MozillaTest while you're at it.

By the way, my apologies for busting things at such a wonderful time.  :-\

Comment 1

[Justin Dolske [:Dolske]]

I tried kicking these from the buildbot admin interface at http://qm-unittest02.mozilla.org:2005/, but nada. The ping command worked, but force build requests just increment the "pending" count and nothing happens.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

fx-win32-tbox is restarted, leaving the others to coop/mikeal.

Comment 3

[Chris Cooper [:coop] (he/him)]

Most of this got taken care of yesterday. Will close out this aft.

Comment 4

[Chris Cooper [:coop] (he/him)]

These all seem to be working again now.