430400 - qm-win2k3-pgo01 is running mochichrome as "browser chrome", and not running browser chrome tests

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P1)

Description

[:Gavin Sharp [email: [e-mail]]]

We have two test suites with "chrome" in the name, so I can see why this might have happened.

1) "browser chrome tests"
   Run with runtests.py --browser-chrome
   mozbuild.py class: MozillaBrowserChromeTest/MozillaWin32BrowserChromeTest

2) "chrome mochitests" or "mochichrome"
   Run with runtests.py --chrome
   mozbuild.py class: MozillaMochichrome/MozillaWin32Mochichrome

Looking at http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/tools/buildbot-configs/testing/unittest/master.cfg&rev=1.25&mark=674-680#674 , the pgo machine is configured incorrectly. It isn't running test 1), and it's running 2) using the wrong name/log parsing class, which leads to bogus "browser 0/0/1" results.

Comment 1

[Rob Campbell [:rc] (:robcee)]

indeed. I fix.

Comment 2

[Rob Campbell [:rc] (:robcee)]

Attachment: fix for mochi* on pgo

fix for different mochitests. Should be same as win2k3 factory above.

Comment 3

[Rob Campbell [:rc] (:robcee)]

Comment on attachment 317708 [details] [diff] [review]
fix for mochi* on pgo

Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/unittest/master.cfg,v  <--  master.cfg
new revision: 1.27; previous revision: 1.26
done

Comment 4

[Rob Campbell [:rc] (:robcee)]

applied to master and reconfigured. Enjoy your breakfasts.