Intermittent webdriver/tests/get_current_url/get.py.ini WPT ERROR with Fission
Categories
(Testing :: geckodriver, defect)
Tracking
(Fission Milestone:M6)
Fission Milestone | M6 |
People
(Reporter: cpeterson, Unassigned)
References
Details
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
if webrender and (os == "linux") and debug and fission: ["PASS", "ERROR"]
Reporter | ||
Comment 2•5 years ago
•
|
||
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #1)
Chris, do you have more details? Any try link?
Sorry. I don't have more details at this time. I'm filing bugs for WPT test cases that have been annotated as not passing with Fission. I haven't personally witnessed these test failures, just the Fission annotations in get.py.ini.
Bug 1622338 will make running running WPT test cases locally with Fission easier.
Reporter | ||
Comment 3•5 years ago
|
||
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.
We're hoping to enable Fission for a subset of Nightly users in early Q3, so we would like WPT tests to be green for Fission by end of Q2. Whether a particular test failure actually blocks shipping Fission is up to the discretion of the feature team. You all would know better than the DOM Fission which test failures are most important.
You can enable Fission when running WPT tests locally using mach wpt --enable-fission
.
Comment 4•5 years ago
|
||
The underlying problem is in Marionette:
[task 2020-03-19T06:39:32.177Z] 06:39:32 INFO - PID 12797 | JavaScript error: chrome://marionette/content/listener.js, line 378: SecurityError: Permission denied to access property "windowUtils" on cross-origin object
This is already covered by bug 1574508.
Updated•5 years ago
|
Description
•