Created attachment 8459252 [details] [diff] [review] enable-debug-e10s We're pretty close to getting debug mochitests green on Linux, so I'd like to start running these tests. Once we get them fully green we can unhide them. I think this patch should do it?
Comment on attachment 8459252 [details] [diff] [review] enable-debug-e10s The patch seems to do it, however, the way that I would suggest going first is to enable only on one tree. The reason is that hiding and unhiding a job across *all* of the tbpl pages is a big pain. I would start by doing something like this: BRANCHES['cedar']['platforms']['linux']['ubuntu32_vm']['debug_unittest_suites'] += MOCHITEST_E10S[:] Once green, we could then enable across all trees. Makes sense?
It looks like cedar is busted right now. Also, we already have holly running e10s tests. We have a holly push from Monday where the Linux debug tests are all green . I also have a try push from last week where everything except M-1 is green with 5 or 6 re-triggers . I did another merge today and we can see if the tests are still green . If they are, can we just enable everywhere?  https://tbpl.mozilla.org/?tree=Holly&rev=8b8c7fcfb310  https://tbpl.mozilla.org/?tree=Try&rev=10ed9f223578  https://tbpl.mozilla.org/?tree=Holly&rev=d820790d9fa0
I don't see debug e10s running on Holly: https://tbpl.mozilla.org/?tree=Holly&rev=d820790d9fa0&showall=1&jobname=e10s Why are the rest of the unit test that orange? Could you also please follow up with someone from releng? I changed teams.
All the normal jobs on Holly are running with e10s enabled. That's why there's so much orange. So if you look at the normal Linux debug jobs on holly, they're running in e10s (and they're green): https://hg.mozilla.org/projects/holly/file/d820790d9fa0/testing/config/mozharness/linux_config.py#l18
Comment on attachment 8459252 [details] [diff] [review] enable-debug-e10s I think this works. Please keep an eye on it once this rolls out; if these don't go green relatively soon after landing, we probably want to back out to avoid burning excess test pool time.
Attachment #8459252 - Flags: review+
Looks like this got deployed and is working!
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.