Recently I tried running the following locally: xvfb-run -a ./mach mochitest dom/workers/test/serviceworkers/ --e10s This gets stuck on the test_privatebrowsing.html chrome mochitest. It seems it starts, but just does not proceed through its expected tests in e10s mode. This does not trigger in automation because we don't run oth in e10s yet, but its annoying for running local tests.
I was just looking at the test for bug 1397365 (where we had a redundant/racy loadURI), and the test looks like it wants to be rewritten from a "chrome" test to a "browser" (chrome) test using ContentTask.spawn() instead of directly reaching into the globals from outside (which would require super-magic CPOWs or something sketchy).
You need to log in before you can comment on or make changes to this bug.