Permanent /webdriver/tests/bidi/log_entry_added/args.py | test_primitive_types[undefined] - setup error: webdriver.error.SessionNotCreatedException: session not created (Requested bidi session, ... when Gecko 96 merges to Beta on 2021-12-06
Categories
(Remote Protocol :: WebDriver BiDi, defect)
Tracking
(firefox-esr91 unaffected, firefox94 unaffected, firefox95 unaffected, firefox96+ verified)
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox94 | --- | unaffected |
| firefox95 | --- | unaffected |
| firefox96 | + | verified |
People
(Reporter: aryx, Assigned: aryx)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 external file)
TEST-UNEXPECTED-ERROR | /webdriver/tests/bidi/log_entry_added/args.py | test_primitive_types[undefined] - setup error: webdriver.error.SessionNotCreatedException: session not created (Requested bidi session, but webSocketUrl capability not found)
...
Bug 1693839 didn't move the disabling added in bug 1742580.
Edit: Wait, bug 1693839 got merged now.
| Assignee | ||
Comment 1•4 years ago
|
||
Bug 1693839 renamed the test file.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Not sure that we understand. Bug 1693839 has been fixed a while ago. And there was bug 1731548 recently which moved the file args.py to console_args.py. But with that patch we also moved the appropriate ini file.
https://hg.mozilla.org/mozilla-central/rev/63cb32ec323baa4489768e0c1d2a8da48cb5d37a
So it's not clear what actually breaks here when a current mozilla-central commit is used for beta uplift.
Comment 3•4 years ago
|
||
Actually there was an upstream merge conflict for web-platform-tests which needed a fix. As it looks like this got messed up and the recent wpt downstream sync renamed this file back to args.py.
As such the meta ini file is correct, but the test name needs to be updated.
Comment 4•4 years ago
|
||
Hm, why is searchfox not showing the args.py file?
https://searchfox.org/mozilla-central/source/testing/web-platform/tests/webdriver/tests/bidi/log_entry_added
It's actually outdated and the new and required file is console_args.py. James, how best can we fix upstream so that it is in sync again?
Comment 5•4 years ago
|
||
I think if you update m-c to the state you want the upstream sync will either fail and I can fix it or will be a noop. So just patch m-c to be correct and I can handle the rest (and apologies for the confusion here, I guess if we are reapplying a sync that got changes upstream, and that created a file that has later been removed, we end up recreating the original file).
Updated•4 years ago
|
Updated•4 years ago
|
Comment 10•4 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 11•4 years ago
|
||
Verified fixed with today's central-as-beta simulation.
Description
•