471638 - [SeaMonkey, Linux] Tests fail after landing bug 465998

Status: VERIFIED FIXED

(Core :: XUL, defect)

Description

[Serge Gautherie (:sgautherie)]

Before:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1230675329.1230679421.7957.gz
Linux comm-central dep unit test on 2008/12/30 14:15:29

After:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1230678949.1230685633.20982.gz
Linux comm-central dep unit test on 2008/12/30 15:15:49
{
...
*** 73588 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/content/tests/widgets/test_popup_button.xul | Too many test timeouts, giving up.

...
*** 5278 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_largemenu.xul | Too many test timeouts, giving up.
}

Regression timeframe:
http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?startdate=2008-12-30+13%3A36%3A05&enddate=2008-12-30+15%3A20%3A51
I guess it would be bug 465998.
(NB: There was 2 comm-central checkins too.)

Comment 1

[Robert Kaiser]

I restarted the metacity window manager on the buildbot slave, which had apparently crashed.
We had the signature of 5 failing mochitests and 8 failing chrome tests before when such a metacity crash had happened. As there was a crash fix involved, it's possible that the crasher bug was what caused metacity to go down in the first place.

Comment 2

[Serge Gautherie (:sgautherie)]

(In reply to comment #1)
> We had the signature of 5 failing mochitests and 8 failing chrome tests before

Ah, these 5+8 numbers reminded me of something, but I didn't know what.

Comment 3

[Robert Kaiser]

OK, starting metacity again fixed the problem. We're green.

Comment 4

[Serge Gautherie (:sgautherie)]

V.Fixed (after one (unrelated) orange)