Closed Bug 1455367 Opened 4 years ago Closed 3 years ago
[wpt-sync] Sync PR 10536 - Update fetch and service worker tests to allow same-origin redirects …
Sync web-platform-tests PR 10536 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/10536 Details from upstream follow. Ben Kelly <email@example.com> wrote: > Update fetch and service worker tests to allow same-origin redirects … > > …with no-cors requests. > > This attempts to align the initial test changes from #9039 with what finally landed in the spec. It also fixes some thing like https-vs-http that crept into the fetch test in the last merge. > > @annevk @mattto @youennf
4 years ago
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=0518b3bc371f185a598c668b2e00b7a95584d52f
Component: web-platform-tests → DOM
Product: Testing → Core
James, now that bug 1455332 has landed can we get this merged?
3 years ago
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=1dc55b950817f34545db1b0db75ce933a4570501
Ran 3 tests and 176 subtests OK : 3 PASS : 176
Looks like its unstuck.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/372d779ec720 [wpt PR 10536] - Update fetch and service worker tests to allow same-origin redirects …, a=testonly
James, it appears that the wpt sync bot left a bunch of old expectations after this merged. For example, redirect-mode.html.ini has: [Redirect 301 in follow redirect and cors mode] expected: FAIL But that is no longer a test case since the test case name has "same-orign" or "cross-origin" added now. Also, we pass all the tests in this file now. Is this a known issue?
Yeah, we don't delete missing expectations because sometimes we get different tests on different configurations, so unless we have a full run of the testsuite across all supported configurations it's not possible to do safely. I will be working on the metadata update code soon, so this seems like a totally reasonable thing to add as an option.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.