commit | 02bfa1b6a029e96b13bebf6dcbf22a379a54219a | [log] [tgz] |
---|---|---|
author | Noam Rosenthal <nrosenthal@chromium.org> | Wed Aug 23 08:16:45 2023 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Aug 23 08:59:52 2023 |
tree | fc9ab4ae7588783809bc013081c30afb288c885d | |
parent | 72748b039e6146f3b0fa2552c028838862b9eafc [diff] |
Revert "LoAF: support approximate source locations for promise resolvers" This reverts commit 07a41b1a0d49acd929ba716332c65ec7c8c55a2b. Reason for revert: performance regression. See https://bugs.chromium.org/p/chromium/issues/detail?id=1475117 Will try to refactor and run pinpoint on the CL with that test. Original change's description: > LoAF: support approximate source locations for promise resolvers > > Attribute the source location of a promise resolver that contributed > to LoAF to the script that created it, e.g. the script that called > fetch(). > > Getting the exact source location of the promise resolver itself > would require capturing a stack trace, which might be too much > overhead, so this is the next best thing. We can revise in the future > whether a shallow stack trace is something we're OK with in some > circumstances. > > Note that it's impossible to get the location of the actual then(), > as that's a microtask that's batched together with all the rest of > the microtasks (e.g. other then()s of the same promise). > > The animation frame monitor maintains a weak map between the promise > resolver and the source location of the event > listener/script-block/callback that was responsible for creating it. > This source location is then used when a promise is resolved and the > resolution task is a long script that contributes to the LoAF. > > Bug: 1392685 > Change-Id: I268ebbbf035b0800a5d1bd61cd939e46533fe064 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4783320 > Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> > Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1186486} Bug: 1392685 Change-Id: I11a4618e5e9be83c116547d63483bae4c8954d13 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4803709 Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/main@{#1187097}
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!