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.
indeed. I fix.
Assignee: nobody → rcampbell
Priority: -- → P1
Created attachment 317708 [details] [diff] [review] fix for mochi* on pgo fix for different mochitests. Should be same as win2k3 factory above.
Attachment #317708 - Flags: review?(ccooper)
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
Attachment #317708 - Attachment filename: pgo-mochi-fix.patch → [checked-in] pgo-mochi-fix.patch
applied to master and reconfigured. Enjoy your breakfasts.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.