I'm not sure why this gets reported as a new failure, they have been failing (on mc and upstream) since end of october. The tests in fail_request/invalid.py.ini have been FAIL for a while for firefox. We don't implement this command at all. See the [wpt.fyi history](https://wpt.fyi/results/webdriver/tests/bidi/network/fail_request/invalid.py) which shows a FAIL status since the end of October. Same goes for the test_response_headers ones, they are marked FAIL since the sync done in Bug 1860524 (https://hg.mozilla.org/integration/autoland/rev/44dcb2922209). But for those 2 I don't remember if this is an expected issue. Sasha: do you understand why those old failures are reported as new here?
Bug 1868353 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm not sure why this gets reported as a new failure, they have been failing (on mc and upstream) since end of october. The tests in fail_request/invalid.py.ini have been FAIL for a while for firefox. We don't implement this command at all. See the [wpt.fyi history](https://wpt.fyi/results/webdriver/tests/bidi/network/fail_request/invalid.py) which shows a FAIL status since the end of October. Same goes for the test_response_headers ones, they are marked FAIL since the sync done in Bug 1860524 (https://hg.mozilla.org/integration/autoland/rev/44dcb2922209). But for those 2 I don't remember if this is an expected issue. Edit: for test_response_headers, the failures make sense, filed https://bugzilla.mozilla.org/show_bug.cgi?id=1868576 Sasha: do you understand why those old failures are reported as new here?