| commit | 0a269ce3bfccdff1b83e2f51917d1de339c11eb5 | [log] [tgz] |
|---|---|---|
| author | Daniel Smith <56164590+DanielRyanSmith@users.noreply.github.com> | Tue Jan 11 23:26:14 2022 |
| committer | GitHub <noreply@github.com> | Tue Jan 11 23:26:14 2022 |
| tree | 72d400bf364a39f223f29552441f9d80e75bfdb4 | |
| parent | 4928cc8d516868267da4be9a5b9a5f7856dd0b65 [diff] |
7660 Avoid CI stability checks timing out (#32202) * allow stability checks to avoid TC timeout by checking times in between repeat runs * fix flake8 issue * remove empty flag to trigger stability checks * some commenting explaining how iterations are being tracked * add --repeat-max-time flag * better descriptors for announcing results If the repeat runs stop early to avoid, timeout, a message will be written in the results explaining so. * cast max_time to timedelta * correct syntax for kwargs * specify kwargs source for run_test_iteration * remove empty css flags tag to trigger stability checks * Add clause to handle an ineffective number of iterations completing * replace unassociated change used to trigger stability checks * Implement changes suggested by @stephenmcgruer * Add only necessary formatting changes to stability * wptrunner reformatting changes suggested by @jgraham * functional changes to stability tests suggested by @jgraham * flake8 changes "line break before binary operator" * change run_tests to return counts object * ensure run_tests return values are properly accessed Now that wptrunner's run_tests returns more than 1 value, the return type will be a tuple for the older variables that expect only 1 value. We need to ensure that we pull the expected first value (boolean) out of that tuple. * run_tests has consistent return values even in fail cases wptrunner's run_tests would return a tuple only if not issues arose while running, and would return only a boolean in the case of some expected issue. Now a tuple is returned in all instances as expected. * Return full counts in TestStatus class run_tests will now return a new TestStatus object rather than returning only the number of iterations run. This will allow for more robust statistics to be shown in the future. * small formatting changes reducing some comments and logs to taking less vertical space. * small wording change TestStatus docstring * Replace counts with TestStatus object forego the use of defaultdict counts keeping track of test info/results and instead use the custom class TestStatus. * convert some log strings to f-strings
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!