641021 - mochitest-browser-chrome debug hangs the XP slaves

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Armen [:armenzg]]

Attachment: disable mochitest-browser-chrome

As mentioned in bug 614955#c46 I had to reboot every XP slave that was taking a mochitest-other because they would hung (hang?) when they reached mochitest-browser-chrome.

The attached patch should fix that. 
This worked on staging.

Comment 1

[Armen [:armenzg]]

Attachment: [screenshot] running mochitest-browser-chrome

I took a not so great screenshot (I hit the Start button by mistake and it would go away) but it shows the two black windows that I have seen on the XP machines that were getting stuck.

I wanted to keep this ftr.

Comment 2

[Armen [:armenzg]]

Landed and reconfigured all masters.
http://hg.mozilla.org/build/buildbot-configs/rev/14112275c382

We now don't run mochitest-browser-chrome for Windows XP on *debug* jobs.

Comment 3

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

(In reply to comment #0)
> As mentioned in bug 614955#c46 I had to reboot every XP slave that was taking a
> mochitest-other because they would hung (hang?) when they reached
> mochitest-browser-chrome.

Rebooting isn't the optimal thing to do in this sort of situation, because the job will get retried (to the master it looks like a network issue dropped the slave), and because there are other test suites that run in mochitest-other. 

The alternative is to ssh into the box, and run 'tasklist'. For mochitest-browser-chrome we have to kill a python process and the firefox one. The python which is buildbot uses about 14000K of memory, so avoid that one. Using the PID's from the tasklist go
  taskkill /pid <pid1> /pid <pid2> /F

Buildbot carries on to run the next step, which is mochiest-a11y.