Fix how CORB async_test(s) work.
Some CORB tests run in parallel, because they use `async_test`. See https://web-platform-tests.org/writing-tests/testharness-api.html#asynchronous-tests: "Keep in mind that other tests could start executing before an Asynchronous Test is finished." This CL fixes such tests, to make sure that they either migrate to `promise_test` [1] or avoid using shared/global state. [1] https://web-platform-tests.org/writing-tests/testharness-api.html#promise-tests says "Unlike Asynchronous Tests, Promise Tests don’t start running until after the previous Promise Test finishes. Under rare circumstances, the next test may begin to execute before the returned promise has settled. Use add_cleanup to register any necessary cleanup actions such as resetting global state that need to happen consistently before the next test starts." Bug: 1011410 Change-Id: Ib369e6cd07aed2daaf6347ae5d6f777a2c0835db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841898 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#706131}
Showing
Please register or sign in to comment