Intermittent webrtc/RTCPeerConnection-generateCertificate.html.ini WPT FAIL with Fission
Categories
(Core :: WebRTC: Signaling, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox75 | --- | wontfix |
firefox76 | --- | wontfix |
firefox77 | --- | wontfix |
firefox78 | --- | wontfix |
People
(Reporter: cpeterson, Assigned: bwc)
References
(Blocks 1 open bug)
Details
if (processor == "x86") and fission and debug: ["FAIL", "PASS"]
if (processor == "x86") and fission and not debug: ["PASS", "FAIL"]
Comment 1•4 years ago
|
||
Hi Chris, is this something you're looking for the WebRTC team to fix? If so, what is your timeline? Thanks!
Reporter | ||
Comment 2•4 years ago
|
||
(In reply to Dan Minor [:dminor] from comment #1)
Hi Chris, is this something you're looking for the WebRTC team to fix?
Yes. The DOM Fission team is relying on feature teams to debug and fix Fission failures in their tests. If the failure looks like a bug in Fission's DOM or IPC changes, you can send the bug back to me.
If so, what is your timeline? Thanks!
We're hoping to enable Fission for a subset of Nightly users in early Q3, so we would like tests to be green for Fission by end of Q2. Whether a particular test failure actually blocks enabling Fission is up to the discretion of the feature team. You all would know better than the DOM Fission which WebRTC test failures are most important. :)
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Hi Jan-Ivar, as we discussed, could you please have a look to see if this is something we want to fix or disable for fission? Thanks!
Reporter | ||
Comment 4•4 years ago
|
||
btw, you can run WPT tests locally with Fission using mach wpt --enable-fission
(from bug 1622338).
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Might be a dupe of 1607735? Does this actually happen anywhere other than windows?
Assignee | ||
Updated•4 years ago
|
Reporter | ||
Comment 6•4 years ago
|
||
(In reply to Byron Campen [:bwc] from comment #5)
Might be a dupe of 1607735? Does this actually happen anywhere other than windows?
This test is annotated as failing on all x86 platforms, regardless of OS. So I think we can close bug 1607735 as a dupe of this bug, since this bug is a superset.
if (processor == "x86") and fission and debug: ["FAIL", "PASS"]
if (processor == "x86") and fission and not debug: ["PASS", "FAIL"]
Assignee | ||
Comment 7•4 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #6)
(In reply to Byron Campen [:bwc] from comment #5)
Might be a dupe of 1607735? Does this actually happen anywhere other than windows?
This test is annotated as failing on all x86 platforms, regardless of OS. So I think we can close bug 1607735 as a dupe of this bug, since this bug is a superset.
if (processor == "x86") and fission and debug: ["FAIL", "PASS"]
if (processor == "x86") and fission and not debug: ["PASS", "FAIL"]
wpt-sync bot did that automatically, and I don't necessarily trust its judgement.
Assignee | ||
Comment 8•4 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b29e9ee6cb5f97e3c0f1ca4307cc1b667d1308b3
Assignee | ||
Updated•4 years ago
|
Reporter | ||
Comment 11•4 years ago
|
||
(In reply to Byron Campen [:bwc] from comment #7)
wpt-sync bot did that automatically, and I don't necessarily trust its judgement.
Oh. I was trying to be helpful and just closed Windows 7 bug 1607735 as a dupe of this bug, but feel free to re-open it that was premature.
Assignee | ||
Comment 12•4 years ago
|
||
I'll just watch the try push, and update here as needed.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 13•4 years ago
|
||
Ok, looks like we need mach try fuzzy --full for the fission tests?
Assignee | ||
Comment 14•4 years ago
|
||
FWIW, the test-windows10-64-qr/opt-web-platform-tests-fis-e10s job seems fine. Maybe it breaks if all of the webrtc wpt are run?
Assignee | ||
Comment 15•4 years ago
|
||
Hopefully more fission tests in here: https://treeherder.mozilla.org/#/jobs?repo=try&revision=419f2e106b0740e36509049361942a1001461868
Assignee | ||
Comment 16•4 years ago
|
||
test-windows10-64-qr/opt-web-platform-tests-fis-e10s for all of webrtc wpt: https://treeherder.mozilla.org/#/jobs?repo=try&revision=40bef52d43ed23b5f1f5af3cd20b593bbc8bc2d3
Assignee | ||
Comment 17•4 years ago
|
||
I haven't seen any failures on these pushes. I will try one last push with the entire wpt suite, just in case.
Assignee | ||
Comment 18•4 years ago
|
||
Assignee | ||
Comment 19•4 years ago
|
||
Yep, running the full suite leads to problems, at least on windows:
This is likely due to known flaws in our timer code on windows (see bug 1402717).
Reporter | ||
Comment 20•4 years ago
|
||
(In reply to Byron Campen [:bwc] from comment #19)
Yep, running the full suite leads to problems, at least on windows:
This is likely due to known flaws in our timer code on windows (see bug 1402717).
Byron, can we close this Fission bug as a dupe of timer bug 1402717? Or do you think there are other Fission-related problems here that need more investigation?
Reporter | ||
Comment 21•4 years ago
|
||
Tracking WPT Fission bugs for Fission M6b (Q2)
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Reporter | ||
Comment 23•4 years ago
|
||
Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.
Description
•