| commit | f2cb066328f2035c20b2a9726febd82056b7ac41 | [log] [tgz] |
|---|---|---|
| author | Javier Fernández García-Boente <jfernandez@igalia.com> | Mon Sep 28 04:05:04 2020 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Sep 28 05:39:44 2020 |
| tree | dcccac0796124683fa44454d6b57ab600daf60d9 | |
| parent | f5492d8c9fb0c43c0b31fedf5dcb80340cda8585 [diff] |
The adjusted_start must be computed based on the part_start In order to create a new ShapeResultView, we use segments of a previous instance, analyzing its runs based on a new index range for the new instance. Since the start/end of the RunInfo structure may be different than the start index of the ShapeResultView, we use an adjusted_start to adapt the logic to the different data structures. We assume that if the passed start_index for the new range is greater than the current run's part start being processed, we should define the new run's start as the difference of these two values. However, we must also ensure that start_index is at least equal to the the part_start value for such run. The problem described in the issue 1130153 comes from the fact that we use the start_index on cases where it's smaller than the run's part_start. This leads to an incorrect (longer than expected) run. Bug: 1130153 Change-Id: Id5dd505baf1f990d2fe7a9406e191979cbd6b9f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2431523 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#811105}
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:
#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.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 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!