| commit | 95e12101852ce37054603845f49056cc9ec0da0a | [log] [tgz] |
|---|---|---|
| author | Andreas Haas <ahaas@chromium.org> | Mon Feb 24 12:50:18 2020 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue Feb 25 13:24:01 2020 |
| tree | ed00d777e9c38cb68869e4a6b56b18fc1302be30 | |
| parent | 45d0e5e00724e4a3bf10b676d09d5b93c814e622 [diff] |
[v8][wasm] Fix WebAssembly streaming tests This CL fixes a test that is checking the wrong behavior at the moment, and disables the test until the fix in V8 lands. Background: The idea of the test is to create an invalid WebAssembly module, and then check that the module is rejected by streaming compilation. The invalid module was created by taking an empty module and adding two '0' bytes at the end. However, two '0' bytes represent an empty unknown section, which was originally accected by the streaming decoder. The test, however, misinterpreted the test result (i.e. "FAIL Invalid code: compileStreaming assert_unreached: Should have rejected: undefined Reached unreachable decoder" a.k.a. FAIL, streaming compilation succeeded unexpectedly) as the error message of the streaming compiler, and then marked it in the test expectations as the expected behavior. The CL changed the test now to add bytes that clearly create an invalid module, and also deleted the invalid test expectations. R=leszeks@chromium.org Bug: v8:10126 Change-Id: Ie49a7a890abd841a85dc9f634308762ea07e5928 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066907 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#743908}
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.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!