Intermittent Fission TIMEOUT or NOTRUN service-workers/service-worker/waiting.https.html.ini | The ServiceWorker objects returned from waiting attribute getter that represent the same service worker are the same objects
Categories
(Core :: DOM: Service Workers, defect, P2)
Tracking
()
People
(Reporter: cpeterson, Assigned: edenchuang)
References
(Blocks 1 open bug)
Details
Intermittent Fission TIMEOUT or NOTRUN service-workers/service-worker/waiting.https.html.ini
[The ServiceWorker objects returned from waiting attribute getter that represent the same service worker are the same objects]
[waiting.https.html]
expected:
if fission and (os == "linux"): ["OK", "TIMEOUT"]
[The ServiceWorker objects returned from waiting attribute getter that represent the same service worker are the same objects]
expected:
if fission and (os == "linux"): ["PASS", "NOTRUN"]
|
Reporter | |
Comment 1•4 years ago
|
||
Jens, these service-worker/waiting.https.html tests fail intermittently for non-Fission, but they intermittently fail for Fission with a different reason code: TIMEOUT or NOTRUN, instead of FAIL. A Service Worker engineer should probably investigate these intermittent Fission failures and decide whether fixing them should block shipping Fission MVP. We plan to start a slow rollout of Fission to the Release channel in Q3.
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 3•4 years ago
|
||
I set this as p2 first to investigate what to do with this intermittent. It could be changed to P3 or P5 if needed.
|
|
Assignee | |
Comment 4•4 years ago
|
||
I think this is not a fission-specific failure.
According to the log from bug 1709970,
https://treeherder.mozilla.org/logviewer?job_id=339003415&repo=mozilla-central
it is not a fission job, and it also got the same unexpected Timeout and NotRun.
The subtest [The ServiceWorker objects returned from waiting attribute getter that represent the same service worker are the same objects] gets NotRun result since the previous subtest [waiting is set after installation] is timeouted.
I think we can remove the "fission" related keyword from .ini. Set this to be a duplicate of bug 1709970.
|
|
Reporter | |
Comment 5•4 years ago
|
||
(In reply to Eden Chuang[:edenchuang] from comment #4)
I think this is not a fission-specific failure.
...
I think we can remove the "fission" related keyword from .ini. Set this to be a duplicate of bug 1709970.
Thanks for checking! In that case, I will update the .ini file and resolve this bug as a duplicate.
|
|
Reporter | |
Comment 6•4 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #5)
(In reply to Eden Chuang[:edenchuang] from comment #4)
I think this is not a fission-specific failure.
...
I think we can remove the "fission" related keyword from .ini. Set this to be a duplicate of bug 1709970.Thanks for checking! In that case, I will update the .ini file and resolve this bug as a duplicate.
btw, I don't think we need to manually remove the "if fission" expectations from waiting.https.html.ini because, IIUC, WPT expectations are updated automatically by the wpt-sync script when a new snapshot of the WPT tests are vendored from upstream.
Description
•