Upstream service wrkr "skipWaiting" tests to WPT

third_party/WebKit/LayoutTests/http/tests/serviceworker/resources/skip-waiting-installed-worker.js

Index: third_party/WebKit/LayoutTests/http/tests/serviceworker/resources/skip-waiting-installed-worker.js
diff --git a/third_party/WebKit/LayoutTests/http/tests/serviceworker/resources/skip-waiting-installed-worker.js b/third_party/WebKit/LayoutTests/http/tests/serviceworker/resources/skip-waiting-installed-worker.js
index 56b97a718034a4000a7a3b9519f452b97abbd999..df9d0700b7ec4ae1e58c4ac65b5fb72d2e4d796a 100644
--- a/third_party/WebKit/LayoutTests/http/tests/serviceworker/resources/skip-waiting-installed-worker.js
+++ b/third_party/WebKit/LayoutTests/http/tests/serviceworker/resources/skip-waiting-installed-worker.js
@@ -24,7 +24,7 @@ self.addEventListener('message', function(event) {
           }
           if (self.state !== 'activating') {
             port.postMessage(
-                'FAIL: Promise should be resolved after worker activated');
+                'This assertion is invalid. See https://crbug.com/725616');

[falken, 2017/05/29 03:54:17]

I'd be more explicit. The negative asserts in this test are a little confusing:

'This assertion passes in current Chromium (i.e., self.state is 'activating'),
but it should fail. See https://crbug.com/725616'

[mike3, 2017/05/29 15:11:49]

Done.

             return;
           }
           port.postMessage('PASS');