tree a804853333817d0c8bb4628629f38eb145789591
parent 7e92ba7b3cee799c6e87487e4a74817d843bac78
author Matt Falkenhagen <falken@chromium.org> 1538061366 -0700
committer Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> 1538062085 -0400

WPT: service worker: Fix potential race in navigation-redirect.https.html.

Before this CL, the test makes a frame which posts a message to the test
window. But if the test fails, we might not consume the message with
`await` and move on the next test. It's possible the next test gets an
unexpected message from the previous test.

I think a related issue caused the timeout after the Clients variant was
added to the test, since the message handler was created after the frame
was created and it was possible the message arrived after that.

Fix things by explicitly asking the frame for the message when we're
ready for it.

Bug: 876223, 778497
Change-Id: I82b8685df2977aeadea7475965ecccf69bd33111
Reviewed-on: https://chromium-review.googlesource.com/1249423
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594723}