[wptrunner] Collect per-test trace events from Chromium #54366
Merged
Conversation
This file contains hidden or 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
When `wpt run --trace-categories` is specified, the trace events [0] are retrieved from an internal ChromeDriver buffer and logged as an `extra` test result field. The trace will be consumed by an event listener on the Chromium side (https://crrev.com/c/6820247) and can be viewed in https://ui.perfetto.dev/. Partially fulfills crbug.com/434017035 [0]: https://developer.chrome.com/docs/chromedriver/logging/performance-log
jonathan-j-lee
force-pushed
the
wptrunner/chrome-tracing
branch
from
8b013be to
03050e2
Compare
wpt-pr-bot
added
infra
wptrunner
|
I tested this both locally in ./wpt run -y chrome infrastructure --metadata infrastructure/metadata --trace-categories=blink.bindings... and in Chromium CI, for both The CI failures are likely unrelated to the PR (#51981 and #54364). |
jcscottiii
approved these changes
Aug 19, 2025
jonathan-j-lee
merged commit 6b05e1d
into
web-platform-tests:master
31 of 34 checks passed
aarongable
pushed a commit
to chromium/chromium
that referenced
this pull request
Aug 22, 2025
The option works like its `run_web_tests.py` counterpart, except the categories are configurable and the trace is in JSON format. The trace events are retrieved from an internal ChromeDriver buffer and written to `layout-test-results/external/wpt/.../test-trace.json`, where they can be downloaded from the results viewer. See web-platform-tests/wpt#54366 for the upstream change this CL depends on. Bug: 434017035 Change-Id: I49195559e4fca6ce54da4428ec26f3fe528eb2bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6820247 Reviewed-by: James Scott <[email protected]> Commit-Queue: Jonathan Lee <[email protected]> Cr-Commit-Position: refs/heads/main@{#1505149}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
wpt run --trace-categoriesis specified, the trace events are retrieved from an internal ChromeDriver buffer and logged as anextratest result field. The trace will be consumed by an event listener on the Chromium side (https://crrev.com/c/6820247) and can be viewed in https://ui.perfetto.dev/.Partially fulfills https://crbug.com/434017035