I will try to determine what test needs to be fixed/disabled: https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=Ubuntu%20VM%2012.04%20cedar%20opt%20test%20mochitest-browser-chrome&rev=df6b18c4a857 For some reason I can see this suite passing on Cedar. Time to enable it everywhere! (unless I'm missing anything).
Not quite so wildly, por favor. It's passing on opt, on that merge, because that merge included the patch from bug 847558 which disabled the test which was failing in most opt runs and many debug runs. It didn't, however, disable the in-content prefs test which is failing in the rest of the debug runs.
I see. This is what happens when I join the party this late. My new URL is: https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=Ubuntu%20VM%2012.04%20cedar
https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=Ubuntu.*VM - you don't want to miss a Linux64-only failure.
and disabling the one test doesn't help, because the next in-content test will fail...we need to find the root cause for this test.
Meh! Do you approve this one? (thanks for .* trick!) https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=Ubuntu.*VM.*mochitest-browser-chrome&rev=df6b18c4a857
Created attachment 748101 [details] ubuntu failure Is this the one we're talking about? (see attachment) The test failing: https://tbpl.mozilla.org/php/getParsedLog.php?id=22821514&tree=Cedar&full=1 08:00:55 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/preferences/in-content/tests/browser_bug410900.js | application timed out after 330 seconds with no output
From looking at Cedar I can see that we want to fix these: https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=Ubuntu.*VM.*debug.*mochitest-browser-chrome So we can stop running them on the Fedora slaves: https://tbpl.mozilla.org/?jobname=Rev3.*mozilla-central%20debug%20test%20mochitest-browser-chrome&showall=1 Is this tracked by bug 847558? Which of the bugs under bug 834725 are real trackers of this one?
I'll 302 jmaher this ^ What are the bugs we need to fix to make Linux/Linux64 debug mochitest-browser-chrome run on Ubuntu?
I filed bug 933680 to track what appears to be the last remaining issue.
(In reply to Joel Maher (:jmaher) from comment #10) > I filed bug 933680 to track what appears to be the last remaining issue. Thanks!
== Status update == Fedora 12x64 debug mochitest-browser-chrome, which runs on rev3 minis, is running on all trunk trees. We want to run the test job on the EC2 machines. There are four dependent bugs, however, I don't know which ones apply to get this bug fixed. IIUC, we want to fix this (un-chunked version): https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=Ubuntu.*x64.*debug.*mochitest-browser-chrome It is specifically to replace this: https://tbpl.mozilla.org/?showall=1&jobname=Fedora%2012x64.*debug.*mochitest-browser-chrome
If anyone gets confused about the "chunked" mochitest-browser-chrome tests, please read catlee's great explanation: https://bugzilla.mozilla.org/show_bug.cgi?id=819963#c66
Felipe is going to help us move this forward.
FTR, fgomes is looking into bug 933680. He made an update there.
fgomes made some more comments there. I'm also going to enable these jobs on Elm. I will add a URL once they're running later this week. bug 981701 is looking into disabling tests.
If bug 982225 (moving to 3 chunks) proves to be the way to go, I assume we can close this bug and all dependent bugs.
= Status update = * Running side-by-side on m-i: https://tbpl.mozilla.org/?tree=Mozilla-Inbound&jobname=Ubuntu.*mochitest-browser-chrome-&showall=1 ** bc1 is the only one left to be greened up ** being fixed in bug 933680
jmaher says that we're ready to look into enabling these chunked mochitest across trunk trees and aurora: https://tbpl.mozilla.org/?tree=Mozilla-Inbound&showall=1&jobname=.*debug.*mochitest-browser-chrome
please run aurora side by side, but trunk trees are much more stable on ec2 and in 3 chunks than I see on inbound
Can this bug be closed?