Closed Bug 1793659 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 36263 - FSA: getUniqueId scaffolding

Categories

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

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox108 fixed)

Status:
RESOLVED FIXED
Milestone:
108 Branch
Tracking Flags:
Tracking Status
firefox108 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Austin Sullivan <asully@chromium.org> wrote:

FSA: getUniqueId scaffolding

Dummy implementation of getUniqueId that allows for developers to start
experimenting with this method behind a flag.

The returned ID is not stable across browsing sessions.

Bug: 1342961
Change-Id: I1938083ca801ec5f3db0264384625cf638523315
Reviewed-on: https://chromium-review.googlesource.com/3933798
WPT-Export-Revision: 66fd428564f93d0b473f0e5e5d37738cb3d2b145

CI Results

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

Total 2 tests and 11 subtests

Status Summary

Firefox

OK : 2
FAIL: 22

Chrome

OK : 2
FAIL: 22

Safari

OK : 2
FAIL: 22

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /fs/FileSystemBaseHandle-getUniqueId.https.any.html [wpt.fyi]
    • identical directory handles return the same ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • different directories return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • different handles for the same directory return the same ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • identical file handles return the same unique ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • different files return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • different handles for the same file return the same ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • two files of the same name in different directories return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • a file and a directory return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • a file and a directory of the same path return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • unique ID of a file handle does not change after writes: FAIL (Chrome: FAIL, Safari: FAIL)
    • unique ID is in GUID version 4 format: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fs/FileSystemBaseHandle-getUniqueId.https.any.worker.html [wpt.fyi]
    • identical directory handles return the same ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • different directories return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • different handles for the same directory return the same ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • identical file handles return the same unique ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • different files return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • different handles for the same file return the same ID: FAIL (Chrome: FAIL, Safari: FAIL)
    • two files of the same name in different directories return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • a file and a directory return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • a file and a directory of the same path return different IDs: FAIL (Chrome: FAIL, Safari: FAIL)
    • unique ID of a file handle does not change after writes: FAIL (Chrome: FAIL, Safari: FAIL)
    • unique ID is in GUID version 4 format: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/55d2f0cdad79 [wpt PR 36263] - FSA: getUniqueId scaffolding, a=testonly https://hg.mozilla.org/integration/autoland/rev/9cf2703afa62 [wpt PR 36263] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/55d2f0cdad79
https://hg.mozilla.org/mozilla-central/rev/9cf2703afa62

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox108: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.