Open
Bug 1182633
Opened 10 years ago
Updated 3 years ago
service workers test_privatebrowsing.html chrome mochitest does not run on e10s
Categories
(Core :: DOM: Service Workers, defect, P3)
Core
DOM: Service Workers
Tracking
()
NEW
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: bkelly, Unassigned)
References
(Blocks 2 open bugs)
Details
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.
Updated•10 years ago
|
Blocks: e10s-tests
tracking-e10s:
--- → +
Reporter | ||
Updated•8 years ago
|
Comment 1•8 years ago
|
||
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).
Updated•7 years ago
|
Priority: -- → P2
Updated•5 years ago
|
Priority: P2 → P3
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•