Closed Bug 1740207 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 31557 - Storage Foundation: read/write tests with non-zero buffer offsets.

Categories

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

task

Tracking

(firefox96 fixed)

RESOLVED FIXED
96 Branch
Tracking Status
firefox96 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Victor Costan <pwnall@chromium.org> wrote:

Storage Foundation: read/write tests with non-zero buffer offsets.

Bug: 1268269
Change-Id: If37da4504cfd2cef725bec0dd19b42bb8108d74a
Reviewed-on: https://chromium-review.googlesource.com/3269671
WPT-Export-Revision: 0fc6ea37e243f9935f3020b59ae5f5fd282193fd

CI Results

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

Total 5 tests and 4 subtests

Status Summary

Firefox

OK : 5
FAIL : 20

Chrome

OK : 5
PASS : 20

Safari

OK : 4
FAIL : 16
ERROR: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/native-io/read_write_async_buffer_offset.tentative.https.any.worker.html
NativeIOFile.write with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.write with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.read with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.read with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
/native-io/read_write_async_buffer_offset.tentative.https.any.html
NativeIOFile.write with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.write with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.read with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.read with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
/native-io/read_write_async_buffer_offset.tentative.https.any.serviceworker.html
NativeIOFile.write with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.write with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.read with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFile.read with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
/native-io/read_write_async_buffer_offset.tentative.https.any.sharedworker.html
NativeIOFile.write with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS)
NativeIOFile.write with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS)
NativeIOFile.read with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS)
NativeIOFile.read with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS)
/native-io/read_write_sync_buffer_offset.tentative.https.any.worker.html
NativeIOFileSync.write with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFileSync.write with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFileSync.read with a Uint8Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)
NativeIOFileSync.read with a Uint16Array accounts for the buffer offset: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bb9766361e95
[wpt PR 31557] - Storage Foundation: read/write tests with non-zero buffer offsets., a=testonly
https://hg.mozilla.org/integration/autoland/rev/ae2ec0ff87a3
[wpt PR 31557] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in before you can comment on or make changes to this bug.