Closed Bug 1830990 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39812 - [wptrunner] Add `--enable-sanitizer` to run all tests as crashtests

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox115 fixed)

Status:
RESOLVED FIXED
Milestone:
115 Branch
Tracking Flags:
Tracking Status
firefox115 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 39812 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/39812
Details from upstream follow.

Jonathan Lee <jonathanjlee@google.com> wrote:

[wptrunner] Add --enable-sanitizer to run all tests as crashtests

Chromium's run_web_tests.py has an --enable-sanitizer flag to run all tests as crash tests. Chromium CI enables this flag for sanitized builds of chrome/content_shell to reduce noise from functional test failures, which are redundant with those from nonsanitized builds.

In crrev.com/c/4099689, this flag was added to the Chromium wptrunner results processor, but this could lead to an inconsistent exit code (nonzero, but no test failures). This change promotes the flag to a Chrome-specific native wptrunner flag to actually run tests as crashtests, since result reporting and evaluating test runs is a core harness responsibility.

Fixes crbug.com/1427892

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Try push failed: decision task FV2J7GGDRNuFehgR6vQ9xg returned error
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/939b1ae98a49 [wpt PR 39812] - [wptrunner] Add `--enable-sanitizer` to run all tests as crashtests, a=testonly

https://hg.mozilla.org/mozilla-central/rev/939b1ae98a49

Status: REOPENED → RESOLVED
Closed: 2 years ago → 2 years ago
status-firefox115: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in before you can comment on or make changes to this bug.