Closed
Bug 1295331
Opened 8 years ago
Closed 3 years ago
Fix an re-enable service-workers/service-worker/appcache-ordering-main.https.html WPT test
Categories
(Core :: DOM: Service Workers, defect, P5)
Core
DOM: Service Workers
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure)
Filed by: philringnalda [at] gmail.com https://treeherder.mozilla.org/logviewer.html#?job_id=1915942&repo=autoland https://queue.taskcluster.net/v1/task/Tlrwnp_WTaGOdhgmRraFMw/runs/0/artifacts/public%2Flogs%2Flive_backing.log
Comment 1•8 years ago
|
||
bkelly: we're disabling appcache-ordering-main.https.html in bug 1305877 because it now fails either consistently or not at all as a result of test chunking changes. A possible explanation of this is something from an earlier test (that either runs or doesn't run depending on how tests are chunked) is throwing off state somewhere in Gecko, causing the test to hang. The Try push at https://treeherder.mozilla.org/#/jobs?repo=try&revision=322875f23cdbb192c82f2e13b1fc842fc6c8e457 demonstrates Linux64 opt passing on buildbot but failing on TaskCluster. (The chunk count is different in each environment.)
Flags: needinfo?(bkelly)
Comment 2•8 years ago
|
||
Sounds good to me. It seems it was previously marked timeout anyway which means we never fixed this test. Lets use this bug as the follow-up to re-enable.
Component: web-platform-tests → DOM: Service Workers
Flags: needinfo?(bkelly)
Product: Testing → Core
Summary: Intermittent TEST-UNEXPECTED-TIMEOUT | /service-workers/service-worker/appcache-ordering-main.https.html | expected OK → Fix an re-enable service-workers/service-worker/appcache-ordering-main.https.html WPT test
Version: Version 3 → unspecified
Updated•8 years ago
|
Blocks: ServiceWorkers-postv1
Updated•7 years ago
|
Updated•7 years ago
|
Priority: -- → P5
Comment 3•3 years ago
|
||
Appcache support was removed.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•