Andrey Lushnikov e57b4b5073 cherry-pick(#12070): fix: propagate exit code in experimental mode (#12133) ... SHA: 5db7ce5964 In experimental ESM mode a child process is forked in order to run the tests. Currently the exit code of this child process is not propagated to the exit code of the parent process, which means that the process exits with a status code of `0` even if some of the tests failed. This makes it difficult to use Playwright in CI in experimental mode, as the CI pipeline as a whole will pass despite the test failures. This change addresses this by propagating the exit code in the case where it is non-zero. Co-authored-by: pierscowburn <me@pierscowburn.com>		2022-02-15 13:25:14 -08:00
..
html-reporter	feat(test-runner): support expect.soft (#11800)	2022-02-02 18:33:51 -08:00
playwright	chore: mark v1.19.0 (#11981)	2022-02-11 09:42:54 -08:00
playwright-chromium	chore: mark v1.19.0 (#11981)	2022-02-11 09:42:54 -08:00
playwright-core	cherry-pick(#12070): fix: propagate exit code in experimental mode (#12133)	2022-02-15 13:25:14 -08:00
playwright-firefox	chore: mark v1.19.0 (#11981)	2022-02-11 09:42:54 -08:00
playwright-test	chore: mark v1.19.0 (#11981)	2022-02-11 09:42:54 -08:00
playwright-webkit	chore: mark v1.19.0 (#11981)	2022-02-11 09:42:54 -08:00
.eslintrc.js	chore: don't write into stdout from the test runner, use reporters instead (#11367)	2022-01-12 19:52:40 -08:00