Closed Bug 865451 Opened 9 years ago Closed 9 years ago
Story - Add support for the new mochitest metro chrome test suite
Metro browser mochitests should be running on inbound, try and mc fairly soon. We'll need to add a new moniker for these tests ('mc' for metro chrome?), which should initially be hidden so we can sort out random orange issues. The tests that run are browser chrome tests that run in the metro browser. We're currently working out some config issues on Cedar in bug 864418. Initial log results can be viewed here - https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=WINNT%206.2%20cedar%20opt%20test%20metro-immersive
Summary: Add support for the new mochitest metro chrome test suite → Story - Add support for the new mochitest metro chrome test suite
Whiteboard: feature=story c=testing u=developer p=0
Assignee: nobody → emorley
Status: NEW → ASSIGNED
Comment on attachment 741800 [details] [diff] [review] Add support for mochitest metro chrome; Review of attachment 741800 [details] [diff] [review]: ----------------------------------------------------------------- ::: js/Data.js @@ +563,5 @@ > /dxr/i.test(name) ? "DXR Index Build" : > /build$/i.test(name) ? "Build" : > // ** Unit tests ** > /mochitest-other/i.test(name) ? "Mochitest Other" : > + /metro-immersive/i.test(name) ? "Mochitest Metro Browser Chrome" : The naming you've used seems fine to me. I can't really say if the above line is correct or not as I have no clue what it does. :)
Attachment #741800 - Flags: review?(jmathies) → review+
Sorry I should have said the r? was more for the naming (rest is just copy pasta of the horrid horrid nested ternaries). https://hg.mozilla.org/webtools/tbpl/rev/ba7fe899ad55
In production :-)
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Thanks for the quick turn around!
wrong bug, this is for tinderbox push log.
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.