Closed Bug 1680413 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 26733 - [Import Maps] Sync tests in WPT and WICG repository (WPT side)

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox85 fixed)

RESOLVED FIXED
85 Branch
Tracking Status
firefox85 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 26733 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/26733
Details from upstream follow.

b'Hiroshige Hayashizaki <hiroshige@chromium.org>' wrote:

[Import Maps] Sync tests in WPT and WICG repository (WPT side)

WPT side: [TBD]
WICG side: https://github.com/WICG/import-maps/pull/237

After these PRs, the data-driven JSON files are identical
in the WPT and WICG repositories.

This CL (WPT side) mostly imports changes from WICG repository.

-expected.txt are added because the spec-side updates
corresponding to the newly imported tests are not yet implemented
in Chromium, and will be removed in upcoming Chromium CLs.

Bug: 848607
Change-Id: Iad3e04a785474ad5844bfcd47dcc7c65691a9a35

Reviewed-on: https://chromium-review.googlesource.com/2570445
WPT-Export-Revision: dc0609c1ac0d72c6bc3a34e24f4a154891752b13

CI Results

Ran 14 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 171 subtests

Status Summary

Firefox

OK : 2
PASS : 72
FAIL : 129

Chrome

OK : 2
PASS : 185
FAIL : 16

Safari

PASS : 4
TIMEOUT: 3
NOTRUN : 25

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/import-maps/data-driven/resolving-internal.https.html
non-HTTPS fetch scheme absolute URLs: about:fetch-scheme: FAIL (Chrome: FAIL, Safari: TIMEOUT)
non-fetch scheme absolute URLs: about:fetch-scheme: FAIL (Chrome: FAIL, Safari: NOTRUN)
non-fetch scheme absolute URLs: mailto:non-fetch-scheme: FAIL (Chrome: FAIL, Safari: NOTRUN)
non-fetch scheme absolute URLs: import:non-fetch-scheme: FAIL (Chrome: FAIL, Safari: NOTRUN)
non-fetch scheme absolute URLs: javascript:non-fetch-scheme: FAIL (Chrome: FAIL, Safari: NOTRUN)
non-fetch scheme absolute URLs: wss:non-fetch-scheme: FAIL (Chrome: FAIL, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: data:text/javascript,console.log('foo'): FAIL (Chrome: FAIL, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: data:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: about:text/foo: FAIL (Chrome: FAIL, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: about:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: blob:text/foo: FAIL (Chrome: FAIL, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: blob:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: blah:text/foo: FAIL (Chrome: FAIL, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: blah:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: http:text/foo: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: http:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: https:text/foo: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: https:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: ftp:text/foo: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: ftp:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: file:text/foo: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: file:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: ws:text/foo: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: ws:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: wss:text/foo: FAIL (Chrome: PASS, Safari: NOTRUN)
URL-like specifiers: Non-special vs. special schemes: wss:text/: FAIL (Chrome: PASS, Safari: NOTRUN)
/import-maps/data-driven/resolving.https.html
Fallback to toplevel and between scopes: should fall back to imports when no scopes match: a: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should fall back to imports when no scopes match: b: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should fall back to imports when no scopes match: c: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should fall back to imports when no scopes match: d: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use a direct scope override: a: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use a direct scope override: b: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use a direct scope override: c: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use a direct scope override: d: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use an indirect scope override: a: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use an indirect scope override: b: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use an indirect scope override: c: FAIL (Chrome: PASS)
Fallback to toplevel and between scopes: should use an indirect scope override: d: FAIL (Chrome: PASS)
Relative URL scope keys: An empty string scope is a scope with import map base URL: a: FAIL (Chrome: PASS)
Relative URL scope keys: An empty string scope is a scope with import map base URL: b: FAIL (Chrome: PASS)
Relative URL scope keys: An empty string scope is a scope with import map base URL: c: FAIL (Chrome: PASS)
Relative URL scope keys: './' scope is a scope with import map base URL's directory: a: FAIL (Chrome: PASS)
Relative URL scope keys: './' scope is a scope with import map base URL's directory: b: FAIL (Chrome: PASS)
Relative URL scope keys: './' scope is a scope with import map base URL's directory: c: FAIL (Chrome: PASS)
Relative URL scope keys: '../' scope is a scope with import map base URL's parent directory: a: FAIL (Chrome: PASS)
Relative URL scope keys: '../' scope is a scope with import map base URL's parent directory: b: FAIL (Chrome: PASS)
Relative URL scope keys: '../' scope is a scope with import map base URL's parent directory: c: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs inside the scope should use the scope if the scope has matching keys: lodash-dot: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs inside the scope should use the scope if the scope has matching keys: lodash-dot/foo: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs inside the scope should use the scope if the scope has matching keys: lodash-dotdot: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs inside the scope should use the scope if the scope has matching keys: lodash-dotdot/foo: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs inside the scope fallback to less specific scope: moment: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs inside the scope fallback to less specific scope: vue: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs inside the scope fallback to toplevel: moment/foo: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs outside a scope shouldn't use the scope even if the scope has matching keys: lodash-dot: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs outside a scope shouldn't use the scope even if the scope has matching keys: lodash-dotdot: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs outside a scope shouldn't use the scope even if the scope has matching keys: lodash-dot/foo: FAIL (Chrome: PASS)
Package-like scenarios: Base URLs outside a scope shouldn't use the scope even if the scope has matching keys: lodash-dotdot/foo: FAIL (Chrome: PASS)
Package-like scenarios: Fallback to toplevel or not, depending on trailing slash match: moment: FAIL (Chrome: PASS)
Package-like scenarios: Fallback to toplevel or not, depending on trailing slash match: moment/foo: FAIL (Chrome: PASS)
Package-like scenarios: package main modules: moment: FAIL (Chrome: PASS)
Package-like scenarios: package main modules: lodash-dot: FAIL (Chrome: PASS)
Package-like scenarios: package main modules: lodash-dotdot: FAIL (Chrome: PASS)
Package-like scenarios: package submodules: moment/foo: FAIL (Chrome: PASS)
Package-like scenarios: package submodules: lodash-dot/foo: FAIL (Chrome: PASS)
Package-like scenarios: package submodules: lodash-dotdot/foo: FAIL (Chrome: PASS)
Package-like scenarios: package names that end in a slash should just pass through: moment/: FAIL (Chrome: PASS)
Package-like scenarios: backtracking via ..: mapped/path: FAIL (Chrome: PASS)
Package-like scenarios: backtracking via ..: mapped/path/: FAIL (Chrome: PASS)
Tricky specifiers: explicitly-mapped specifiers that happen to have a slash: package/withslash: FAIL (Chrome: PASS)
Tricky specifiers: specifier with punctuation: .: FAIL (Chrome: PASS)
Tricky specifiers: specifier with punctuation: ..: FAIL (Chrome: PASS)
Tricky specifiers: specifier with punctuation: ..: FAIL (Chrome: PASS)
Tricky specifiers: specifier with punctuation: %2E: FAIL (Chrome: PASS)
Tricky specifiers: specifier with punctuation: %2F: FAIL (Chrome: PASS)
URL-like specifiers: Ordinary URL-like specifiers: https://example.com/lib/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: Ordinary URL-like specifiers: https://///example.com/lib/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: Ordinary URL-like specifiers: /lib/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: Ordinary URL-like specifiers: https://example.com/app/dotrelative/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: Ordinary URL-like specifiers: ../app/dotrelative/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: Ordinary URL-like specifiers: https://example.com/dotdotrelative/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: Ordinary URL-like specifiers: ../dotdotrelative/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: Import map entries just composed from / and .: https://example.com/: FAIL (Chrome: PASS)
URL-like specifiers: Import map entries just composed from / and .: /: FAIL (Chrome: PASS)
URL-like specifiers: Import map entries just composed from / and .: ../: FAIL (Chrome: PASS)
URL-like specifiers: Import map entries just composed from / and .: https://example.com/app/: FAIL (Chrome: PASS)
URL-like specifiers: Import map entries just composed from / and .: /app/: FAIL (Chrome: PASS)
URL-like specifiers: Import map entries just composed from / and .: ../app/: FAIL (Chrome: PASS)
URL-like specifiers: prefix-matched by keys with trailing slashes: /test/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: prefix-matched by keys with trailing slashes: https://example.com/app/test/foo.mjs: FAIL (Chrome: PASS)
URL-like specifiers: should use the last entry's address when URL-like specifiers parse to the same absolute URL: /test: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (relative URLs): /test/..: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (relative URLs): /test/../backtrack: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (relative URLs): /test/../../backtrack: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (relative URLs): /test/../../../backtrack: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (absolute URLs): https://example.com/test/..: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (absolute URLs): https://example.com/test/../backtrack: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (absolute URLs): https://example.com/test/../../backtrack: FAIL (Chrome: PASS)
URL-like specifiers: backtracking (absolute URLs): https://example.com/test/../../../backtrack: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scope without trailing slash only: Non-trailing-slash base URL (exact match): moment: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scope without trailing slash only: Non-trailing-slash base URL (exact match): moment/foo: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scope with trailing slash only: Trailing-slash base URL (exact match): moment: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scope with trailing slash only: Trailing-slash base URL (exact match): moment/foo: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scope with trailing slash only: Subpath base URL (prefix match): moment: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scope with trailing slash only: Subpath base URL (prefix match): moment/foo: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scopes with and without trailing slash: Non-trailing-slash base URL (exact match): moment: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scopes with and without trailing slash: Non-trailing-slash base URL (exact match): moment/foo: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scopes with and without trailing slash: Trailing-slash base URL (exact match): moment: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scopes with and without trailing slash: Trailing-slash base URL (exact match): moment/foo: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scopes with and without trailing slash: Subpath base URL (prefix match): moment: FAIL (Chrome: PASS)
Exact vs. prefix based matching: Scopes with and without trailing slash: Subpath base URL (prefix match): moment/foo: FAIL (Chrome: PASS)
should favor the most-specific key: Overlapping entries with trailing slashes: a: FAIL (Chrome: PASS)
should favor the most-specific key: Overlapping entries with trailing slashes: a/: FAIL (Chrome: PASS)
should favor the most-specific key: Overlapping entries with trailing slashes: a/x: FAIL (Chrome: PASS)
should favor the most-specific key: Overlapping entries with trailing slashes: a/b: FAIL (Chrome: PASS)
should favor the most-specific key: Overlapping entries with trailing slashes: a/b/: FAIL (Chrome: PASS)
should favor the most-specific key: Overlapping entries with trailing slashes: a/b/c: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: null/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: null/b/c/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: invalid-url/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: invalid-url/b/c/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: without-trailing-slashes/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: without-trailing-slashes/b/c/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: prefix-resolution-error/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to less-specific prefixes: prefix-resolution-error/b/c/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to absolute URL parsing: https://example.com/null: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to absolute URL parsing: https://example.com/invalid-url: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to absolute URL parsing: https://example.com/without-trailing-slashes/x: FAIL (Chrome: PASS)
Entries with errors shouldn't allow fallback: No fallback to absolute URL parsing: https://example.com/prefix-resolution-error/x: FAIL (Chrome: PASS)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/12df026355e8 [wpt PR 26733] - [Import Maps] Sync tests in WPT and WICG repository (WPT side), a=testonly https://hg.mozilla.org/integration/autoland/rev/3ec3ed991603 [wpt PR 26733] - Update wpt metadata, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1d18c3be1be9 [wpt PR 26733] - [Import Maps] Sync tests in WPT and WICG repository (WPT side), a=testonly https://hg.mozilla.org/integration/autoland/rev/f05818dac52b [wpt PR 26733] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in before you can comment on or make changes to this bug.