The change in test/fixtures/wpt/common/sab.js is due to additional changes beyond web-platform-tests/wpt#27152 that were picked up by the update. It adds additional checks to avoid tests passing when they should not. Unfortunately that means we have more test failures and I had to mark additional test files as expecting a failure. I don't see any way to mark the tests as expecting a failure except at the file level from the current excludes.

@joyeecheung can you confirm that in terms of excluding tests that fail there is no better way to handle excluding the tests than what I've done?

@mhdawson You can use "skip" instead of "fail" if you don't need the test expectation to be changed once the failure is fixed. But using "fail" is OK as well, and it prompts people to update the expectation.

@joyeecheung thanks

CI: https://ci.nodejs.org/job/node-test-pull-request/35707/

Issue already open for test which failed in CI #36867

CI: https://ci.nodejs.org/job/node-test-pull-request/35737/

Resume build to try to get to green: https://ci.nodejs.org/job/node-test-pull-request/35737/

CI: https://ci.nodejs.org/job/node-test-pull-request/35760/

One more attempt: https://ci.nodejs.org/job/node-test-pull-request/35760/ as there was another unrelated failure (build time out)

Landed in 9603e4a