commit | 8ce3c82fb7f762b60e37918d56c7c99bfe4dde76 | [log] [tgz] |
---|---|---|
author | Ulan Degenbaev <ulan@chromium.org> | Mon Jan 20 11:23:45 2020 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Jan 20 11:36:24 2020 |
tree | 60d83909dc7aaa578b937c4a6fc3c324976908f4 | |
parent | ab8f451eb39eb198584d547f5d965ef54df2a86a [diff] |
Implement performance.measureMemory with per-frame sizes This uses a new v8::Isolate::MeasureMemory API to compute the JS memory footprint of each v8::Context that has the same security origin and the same JS agent as the calling context does. The V8 API takes a delegate with two methods that are implemented here: 1) ShouldMeasure(context) for selecting the contexts to measure. It fetches the security origin and the JS agent of a context by going through Context => ExecutionContext. 2) MeasurementComplete(context_sizes, unattributed_size) is called by V8 when the measurement is done. The function constructs an object representing the result and resolves the promise with it. # Disable audit_non_blink_usage std::vector check per reviewer's comment NOPRESUBMIT=True Bug: 973627 Change-Id: Ibd0fb3463978184f1d467be306063d1f40105fda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986795 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#733300}
The web-platform-tests Project is a W3C-coordinated attempt to build 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:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf 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.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 http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
In the vast majority of cases the only upstream branch that you should need to care about is master
. If you see other branches in the repository, you can generally safely ignore them.
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!