Upstream service worker "register" tests to WPT

Upstream service worker "register" tests to WPT

**register-default-scope**

This test exists in both WPT and the Chromium project tree. Because they
differ only in implementation details of the testing infrastructure, the
Chromium-specific version may be removed without affecting test coverage
in the Chromium project.

**register-link-element**

This test was previously re-located to the Web Platform Tests project
[1], but its corresponding "expectations" file was mistakenly persisted.
Remove that file.

[1] See commit e46007715a723c2219f49db6199f1af09cbbc7db in the Chromium
    project

**register-same-scope-different-script-url**

This test exists in both WPT and the Chromium project tree. The WPT
version is slightly weaker because it accounts for a condition that is
not possible according to the latest version of the Service Workers
specification [2].

> # Install
>
> [...]
>
> 17. Run the Update Registration State algorithm passing registration,
>     "installing" and null as the arguments.
> 18. Run the Update Worker State algorithm passing registration’s
>     waiting worker and installed as the arguments.
> 19. Invoke Finish Job with job.
> 20. Wait for all the tasks queued by Update Worker State invoked in
>     this algorithm have executed.
> 21. Invoke Try Activate with registration.

Due to step 20, worker activation does not occur until all prior tasks
(which includes microtasks such as the Promise handler microtask created
in the test's body) have executed.

Remove the conditional logic from the WPT version and remove the
Chromium test file.

[2] https://w3c.github.io/ServiceWorker/#installation-algorithm,
    retrieved on 2017-05-16

**register-wait-forever-in-install-worker**

The Web Platform Tests project maintains a more rigorous version of this
test, but because that version currently fails in Chromium, this version
cannot be removed without negatively effecting test coverage.

Re-name the test file and add an in-line comment to document the test's
deprecated status.

**register-foreign-fetch-error**

Update URLs to suitable values for the Web Platform Tests project.

BUG=688116, 723037
R=falken@chromium.org

Review-Url: https://codereview.chromium.org/2892473003
Cr-Commit-Position: refs/heads/master@{#472636}
Committed: https://chromium.googlesource.com/chromium/src/+/9190eb27531ee100bcb83450c9c32c5568531afd

[mike3, 2017-05-16 22:17:49]

Description was changed from

==========
Upstream service worker "register" tests to WPT

**register-default-scope**

This test exists in both WPT and the Chromium project tree. Because they
differ only in implementation details of the testing infrastructure, the
Chromium-specific version may be removed without affecting test coverage
in the Chromium project.

**register-link-element**

This test was previously re-located to the Web Platform Tests project
[1], but its corresponding "expectations" file was mistakenly persisted.
Remove that file.

**register-same-scope-different-script-url**

This test exists in both WPT and the Chromium project tree. The WPT
version is slightly weaker because it accounts for a condition that is
not possible according to the latest version of the Service Workers
specification [2].

> # Install
>
> [...]
>
> 17. Run the Update Registration State algorithm passing registration,
>     "installing" and null as the arguments.
> 18. Run the Update Worker State algorithm passing registration’s
>     waiting worker and installed as the arguments.
> 19. Invoke Finish Job with job.
> 20. Wait for all the tasks queued by Update Worker State invoked in
>     this algorithm have executed.
> 21. Invoke Try Activate with registration.

Due to step 20, worker activation does not occur until all prior tasks
(which includes microtasks such as the Promise handler microtask created
in the test's body) have executed.

Remove the conditional logic from the WPT version and remove the
Chromium test file.

[1] See commit e46007715a723c2219f49db6199f1af09cbbc7db in the Chromium
    project
[2] https://w3c.github.io/ServiceWorker/#installation-algorithm,
    retrieved on 2017-05-16

**register-wait-forever-in-install-worker**

The Web Platform Tests project maintains a more rigorous version of this
test, but because that version currently fails in Chromium, this version
cannot be removed without negatively effecting test coverage.

Re-name the test file and add an in-line comment to document the test's
deprecated status.

**register-foreign-fetch-error**

Update URLs to suitable values for the Web Platform Tests project.

BUG=688116, 723037
R=falken@chromium.org
==========

to

==========
Upstream service worker "register" tests to WPT

**register-default-scope**

This test exists in both WPT and the Chromium project tree. Because they
differ only in implementation details of the testing infrastructure, the
Chromium-specific version may be removed without affecting test coverage
in the Chromium project.

**register-link-element**

This test was previously re-located to the Web Platform Tests project
[1], but its corresponding "expectations" file was mistakenly persisted.
Remove that file.

[1] See commit e46007715a723c2219f49db6199f1af09cbbc7db in the Chromium
    project

**register-same-scope-different-script-url**

This test exists in both WPT and the Chromium project tree. The WPT
version is slightly weaker because it accounts for a condition that is
not possible according to the latest version of the Service Workers
specification [2].

> # Install
>
> [...]
>
> 17. Run the Update Registration State algorithm passing registration,
>     "installing" and null as the arguments.
> 18. Run the Update Worker State algorithm passing registration’s
>     waiting worker and installed as the arguments.
> 19. Invoke Finish Job with job.
> 20. Wait for all the tasks queued by Update Worker State invoked in
>     this algorithm have executed.
> 21. Invoke Try Activate with registration.

Due to step 20, worker activation does not occur until all prior tasks
(which includes microtasks such as the Promise handler microtask created
in the test's body) have executed.

Remove the conditional logic from the WPT version and remove the
Chromium test file.

[2] https://w3c.github.io/ServiceWorker/#installation-algorithm,
    retrieved on 2017-05-16

**register-wait-forever-in-install-worker**

The Web Platform Tests project maintains a more rigorous version of this
test, but because that version currently fails in Chromium, this version
cannot be removed without negatively effecting test coverage.

Re-name the test file and add an in-line comment to document the test's
deprecated status.

**register-foreign-fetch-error**

Update URLs to suitable values for the Web Platform Tests project.

BUG=688116, 723037
R=falken@chromium.org
==========

[mike3, 2017-05-16 22:18:39]

Hey Matt, here's another batch of test migrations. Mind taking a look?

[falken, 2017-05-17 07:59:50]

lgtm

[mike3, 2017-05-17 14:47:10]

The CQ bit was checked by mike@mikepennisi.com

[commit-bot: I haz the power, 2017-05-17 14:47:53]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-17 15:38:52]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-17 15:38:53]

Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[mike3, 2017-05-17 15:47:12]

On 2017/05/17 15:38:53, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

Looks like this build got tripped up by an unrelated flaky test:

>     Run on OS: 'Ubuntu-14.04'
>     Total tests: 66317
>     * Passed: 53994 (53914 expected, 80 unexpected)
>     * Skipped: 11509 (11509 expected, 0 unexpected)
>     * Failed: 769 (767 expected, >>>2 unexpected<<<)
>     * Flaky: 45 (45 expected, 0 unexpected)
>
>     Unexpected Failures:
>     * http/tests/dom/script-module-load-incomplete-no-crash.html
>     *
virtual/mojo-loading/http/tests/dom/script-module-load-incomplete-no-crash.html

Should I just check the "Commit" box again? Is there anything I should do to
report this unexpected error? Or maybe mark it as flaky as part of this CL?

[falken, 2017-05-18 01:25:27]

On 2017/05/17 15:47:12, mike3 wrote:
> On 2017/05/17 15:38:53, commit-bot: I haz the power wrote:
> > Try jobs failed on following builders:
> >   linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
> >
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
> 
> Looks like this build got tripped up by an unrelated flaky test:
> 
> >     Run on OS: 'Ubuntu-14.04'
> >     Total tests: 66317
> >     * Passed: 53994 (53914 expected, 80 unexpected)
> >     * Skipped: 11509 (11509 expected, 0 unexpected)
> >     * Failed: 769 (767 expected, >>>2 unexpected<<<)
> >     * Flaky: 45 (45 expected, 0 unexpected)
> >
> >     Unexpected Failures:
> >     * http/tests/dom/script-module-load-incomplete-no-crash.html
> >     *
>
virtual/mojo-loading/http/tests/dom/script-module-load-incomplete-no-crash.html
> 
> Should I just check the "Commit" box again? Is there anything I should do to
> report this unexpected error? Or maybe mark it as flaky as part of this CL?

Yep, just keep trying.

[falken, 2017-05-18 01:25:35]

The CQ bit was checked by falken@chromium.org

[commit-bot: I haz the power, 2017-05-18 01:28:21]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-18 03:30:22]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1495070735955490, "parent_rev":
"8aaa656f06ce8379a55bf81fa4cdca123ff43485", "commit_rev":
"9190eb27531ee100bcb83450c9c32c5568531afd"}

[commit-bot: I haz the power, 2017-05-18 03:30:32]

Description was changed from

==========
Upstream service worker "register" tests to WPT

**register-default-scope**

This test exists in both WPT and the Chromium project tree. Because they
differ only in implementation details of the testing infrastructure, the
Chromium-specific version may be removed without affecting test coverage
in the Chromium project.

**register-link-element**

This test was previously re-located to the Web Platform Tests project
[1], but its corresponding "expectations" file was mistakenly persisted.
Remove that file.

[1] See commit e46007715a723c2219f49db6199f1af09cbbc7db in the Chromium
    project

**register-same-scope-different-script-url**

This test exists in both WPT and the Chromium project tree. The WPT
version is slightly weaker because it accounts for a condition that is
not possible according to the latest version of the Service Workers
specification [2].

> # Install
>
> [...]
>
> 17. Run the Update Registration State algorithm passing registration,
>     "installing" and null as the arguments.
> 18. Run the Update Worker State algorithm passing registration’s
>     waiting worker and installed as the arguments.
> 19. Invoke Finish Job with job.
> 20. Wait for all the tasks queued by Update Worker State invoked in
>     this algorithm have executed.
> 21. Invoke Try Activate with registration.

Due to step 20, worker activation does not occur until all prior tasks
(which includes microtasks such as the Promise handler microtask created
in the test's body) have executed.

Remove the conditional logic from the WPT version and remove the
Chromium test file.

[2] https://w3c.github.io/ServiceWorker/#installation-algorithm,
    retrieved on 2017-05-16

**register-wait-forever-in-install-worker**

The Web Platform Tests project maintains a more rigorous version of this
test, but because that version currently fails in Chromium, this version
cannot be removed without negatively effecting test coverage.

Re-name the test file and add an in-line comment to document the test's
deprecated status.

**register-foreign-fetch-error**

Update URLs to suitable values for the Web Platform Tests project.

BUG=688116, 723037
R=falken@chromium.org
==========

to

==========
Upstream service worker "register" tests to WPT

**register-default-scope**

This test exists in both WPT and the Chromium project tree. Because they
differ only in implementation details of the testing infrastructure, the
Chromium-specific version may be removed without affecting test coverage
in the Chromium project.

**register-link-element**

This test was previously re-located to the Web Platform Tests project
[1], but its corresponding "expectations" file was mistakenly persisted.
Remove that file.

[1] See commit e46007715a723c2219f49db6199f1af09cbbc7db in the Chromium
    project

**register-same-scope-different-script-url**

This test exists in both WPT and the Chromium project tree. The WPT
version is slightly weaker because it accounts for a condition that is
not possible according to the latest version of the Service Workers
specification [2].

> # Install
>
> [...]
>
> 17. Run the Update Registration State algorithm passing registration,
>     "installing" and null as the arguments.
> 18. Run the Update Worker State algorithm passing registration’s
>     waiting worker and installed as the arguments.
> 19. Invoke Finish Job with job.
> 20. Wait for all the tasks queued by Update Worker State invoked in
>     this algorithm have executed.
> 21. Invoke Try Activate with registration.

Due to step 20, worker activation does not occur until all prior tasks
(which includes microtasks such as the Promise handler microtask created
in the test's body) have executed.

Remove the conditional logic from the WPT version and remove the
Chromium test file.

[2] https://w3c.github.io/ServiceWorker/#installation-algorithm,
    retrieved on 2017-05-16

**register-wait-forever-in-install-worker**

The Web Platform Tests project maintains a more rigorous version of this
test, but because that version currently fails in Chromium, this version
cannot be removed without negatively effecting test coverage.

Re-name the test file and add an in-line comment to document the test's
deprecated status.

**register-foreign-fetch-error**

Update URLs to suitable values for the Web Platform Tests project.

BUG=688116, 723037
R=falken@chromium.org

Review-Url: https://codereview.chromium.org/2892473003
Cr-Commit-Position: refs/heads/master@{#472636}
Committed:
https://chromium.googlesource.com/chromium/src/+/9190eb27531ee100bcb83450c9c3...
==========

[commit-bot: I haz the power, 2017-05-18 03:30:40]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/9190eb27531ee100bcb83450c9c3...