-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[wptrunner] Run
--enable-sanitizer
tests with their own executors (#…
…49235) Running non-crashtests with the crashtest executor likely doesn't provide high-fidelity coverage because the test completes on the `load` event by default. This means that code paths normally exercised after the `load` event aren't actually run under sanitization. Also, some tests require testdriver, which the crashtest executor doesn't implement yet, to progress. Now, simply run each test with its corresponding type's executor and suppress functional failures (i.e., not timeout or crash) at the end. This also simplifies the result coercion, which didn't interact correctly with #47903. Tested locally: ```sh ./wpt run -y chrome infrastructure --metadata infrastructure/metadata --enable-sanitizer ```
- Loading branch information
1 parent
0dc40f3
commit d19c517
Showing
3 changed files
with
32 additions
and
63 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters