commit | b8e9469a49469720bb72a078c4ecde798daa70f5 | [log] [tgz] |
---|---|---|
author | Noam Rosenthal <nrosenthal@chromium.org> | Wed Mar 08 08:23:16 2023 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Mar 08 08:37:26 2023 |
tree | 1630f2bc4806346cdccbb6d1fa53e1d6998e8a97 | |
parent | c95d15338d3d4380beffb8b1b8dda62a8d746ab9 [diff] |
LoAF: Initial support for long scripts AnimationFrameMonitor signs into the probe system to track scripts. Scripts that are 5ms or longer that are part of a LoAF (long amimation frame) are reported as one of the LoAF entry. Since some of the probes can be recursive, and also layouts/styles can be recursive, AnimationFrameTimingMonitor maintains a little state machine so that only the top-level scripts are captured: - CompileAndRunScript is called for a <script> tag. - ExecuteScript is called for a script tag (after compilation) and also when an imported module is executed. - UserCallback is called specifically for callbacks who implemented it. - CallFunction is called *a lot* and is there to collect source location for the top level script. - WillHandlePromise is added. Note that task that begin with a promise resolution end only when the next microtask queue is emptied. Note the following: - Only script *entry points* are reported, as in, there are no recursions or time-overlaps between scripts. - To reduce overhead, bookekeping is done once it's clear that the script is longer than 5ms. If this still creates too much overhead, we can increase the number and measure even longer scripts only. - The state machine is somewhat similar to the one in PerformanceMonitor. However, the two classes have a different lifecycle and PerformanceMonitor has a lot of legacy, so copying some of the logic seemed less costly than trying to unify. Missing pieces: - Not all the user callbacks are measured/probed, e.g. PerformanceObserver callbacks. This would require a lot of detail and fine-tuning. - At first, PromiseResolver-based entry points don't have a lot of details, e.g. source location and name. This will be done in a later phase. - Queue time and presentation time are still missing. Explainer: https://github.com/w3c/longtasks/blob/loaf-explainer/loaf-explainer.md Design doc: https://docs.google.com/document/d/1SeMd4KbXWZf0ZnRSMvYhjSBpXPBln5xrRyTu2Gr68BY/edit# Change-Id: I57b62ab51b3f1ab28bbfbcc2d992df4cc10d38ec Bug: 1392685 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268371 Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org> Cr-Commit-Position: refs/heads/main@{#1114430}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave
- For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!