mach test no longer works for wpt tests
Categories
(Testing :: web-platform-tests, defect)
Tracking
(firefox-esr102 unaffected, firefox-esr115 unaffected, firefox117 unaffected, firefox118 unaffected, firefox119 fixed)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox117 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jgraham)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
I get this error every time I try to run wdspec tests locally:
TypeError: wptrunner.browsers.firefox.executor_kwargs() got multiple values for keyword argument 'subsuite'
STRs:
- run
./mach test testing/web-platform/tests/webdriver/tests/bidi/browsing_context/user_prompt_closed/user_prompt_closed.py
Note that ./mach wpt
still works, only the ./mach test
shortcut is broken
Comment 1•2 years ago
|
||
Isn't that actually bug 1849754 which regressed it? Bug 1849951 doesn't show any changes in this call stack.
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1849951
Reporter | ||
Comment 3•2 years ago
|
||
(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #1)
Isn't that actually bug 1849754 which regressed it? Bug 1849951 doesn't show any changes in this call stack.
Uh good catch. Not sure how I came up with the other bug number, the bisect did point to 1849754
Comment 4•2 years ago
|
||
James given that you are the original author of the regressor, could you please have a look?
Assignee | ||
Comment 5•2 years ago
|
||
Unfortunately mach test
makes unverified assumptions about the top
level kwargs of all test suites. This broke wpt because it was passing
around a subsuite
argument that was previously ignored, but recently
caused a conflict in functions with signatures like
function(subsuite, **kwargs).
Fow now just remove the argument in the part of the wpt frontend that
handles data expected to be from mach test
.
Updated•2 years ago
|
Assignee | ||
Comment 6•2 years ago
|
||
mach test
was unconditionally calling shutdown()
on the logger,
which doesn't work if the harness (reasonably) already shut down the
logger itself. Add a new property to check if the logger has been shut
down, and check it before calling shutdown.
Comment 9•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/be2a2dbdf656
https://hg.mozilla.org/mozilla-central/rev/5baf76c5d8f1
Description
•