Closed Bug 1733768 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 30996 - Add Datagrams WPTs for WebTransport

Categories

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

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

Tracking

(firefox95 fixed)

Status:
RESOLVED FIXED
Milestone:
95 Branch
Tracking Flags:
Tracking Status
firefox95 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Nidhi Jaju <nidhijaju@chromium.org> wrote:

Add Datagrams WPTs for WebTransport

This CL adds 4 test cases related to datagrams:

  • echoing datagrams
  • reading & writing datagrams before a session is established
  • checking outgoingHighWaterMark & incomingHighWaterMark
    works properly

Bug: 1201569
Change-Id: I0feb8aee5131f3626da38b3cde65a0765bf40207
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3184855
Commit-Queue: Nidhi Jaju \<nidhijaju@chromium.org>
Reviewed-by: Yutaka Hirano \<yhirano@chromium.org>
Reviewed-by: Kenichi Ishibashi \<bashi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#926238}

CI Results

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

Total 18 tests and 3 subtests

Status Summary

Firefox

OK : 14[Gecko-android-em-7.0-x86_64-lite-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-qr-opt-geckoview, Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt, Gecko-linux1804-64-tsan-qr-opt, Gecko-windows10-32-2004-qr-debug, Gecko-windows10-32-2004-qr-opt, Gecko-windows10-64-2004-qr-debug, Gecko-windows10-64-2004-qr-opt] 18[GitHub]
FAIL : 82[Gecko-android-em-7.0-x86_64-lite-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-qr-opt-geckoview, Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt, Gecko-linux1804-64-tsan-qr-opt, Gecko-windows10-32-2004-qr-debug, Gecko-windows10-32-2004-qr-opt, Gecko-windows10-64-2004-qr-debug, Gecko-windows10-64-2004-qr-opt] 94[GitHub]

Chrome

OK : 5
PASS : 37
FAIL : 43
TIMEOUT: 6
ERROR : 9
NOTRUN : 4

Safari

OK : 14
FAIL : 71
ERROR : 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/webtransport/connect.any.sharedworker.html
WebTransport connection succeeds with status code 200: FAIL
WebTransport connection succeeds with status code 204: FAIL
WebTransport connection fails with status code 301: FAIL
WebTransport connection fails with status code 401: FAIL
WebTransport connection fails with status code 404: FAIL
Echo back request headers: FAIL (Chrome: FAIL)
Cookie header is not echoed back: FAIL (Chrome: FAIL)
WebTransport session is established with status code 200: FAIL (Chrome: FAIL)
WebTransport session is established with status code 204: FAIL (Chrome: FAIL)
WebTransport session establishment fails with status code 301: FAIL (Chrome: FAIL)
WebTransport session establishment with status code 401: FAIL (Chrome: FAIL)
WebTransport session establishment fails with status code 404: FAIL (Chrome: FAIL)
/webtransport/connect.any.serviceworker.html
WebTransport connection succeeds with status code 200: FAIL
WebTransport connection succeeds with status code 204: FAIL
WebTransport connection fails with status code 301: FAIL
WebTransport connection fails with status code 401: FAIL
WebTransport connection fails with status code 404: FAIL
Echo back request headers: FAIL (Chrome: FAIL, Safari: FAIL)
Cookie header is not echoed back: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session is established with status code 200: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session is established with status code 204: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session establishment fails with status code 301: FAIL (Chrome: PASS, Safari: FAIL)
WebTransport session establishment with status code 401: FAIL (Chrome: PASS, Safari: FAIL)
WebTransport session establishment fails with status code 404: FAIL (Chrome: PASS, Safari: FAIL)
/webtransport/connect.any.worker.html
WebTransport connection succeeds with status code 200: FAIL
WebTransport connection succeeds with status code 204: FAIL
WebTransport connection fails with status code 301: FAIL
WebTransport connection fails with status code 401: FAIL
WebTransport connection fails with status code 404: FAIL
Echo back request headers: FAIL (Chrome: FAIL, Safari: FAIL)
Cookie header is not echoed back: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session is established with status code 200: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session is established with status code 204: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session establishment fails with status code 301: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session establishment with status code 401: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session establishment fails with status code 404: FAIL (Chrome: FAIL, Safari: FAIL)
/webtransport/connect.any.html
WebTransport connection succeeds with status code 200: FAIL
WebTransport connection succeeds with status code 204: FAIL
WebTransport connection fails with status code 301: FAIL
WebTransport connection fails with status code 401: FAIL
WebTransport connection fails with status code 404: FAIL
Echo back request headers: FAIL (Chrome: FAIL, Safari: FAIL)
Cookie header is not echoed back: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session is established with status code 200: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session is established with status code 204: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session establishment fails with status code 301: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session establishment with status code 401: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport session establishment fails with status code 404: FAIL (Chrome: FAIL, Safari: FAIL)
/webtransport/constructor.any.serviceworker.html
WebTransport constructor should reject URL 'null': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL '': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'no-scheme': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'http://example.com/': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'quic-transport://example.com/': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https:///': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https://example.com/#failing': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https://web-platform.test:999999/': FAIL (Chrome: PASS, Safari: FAIL)
Connection to port 0 should fail: FAIL (Chrome: PASS, Safari: FAIL)
/webtransport/constructor.any.sharedworker.html
WebTransport constructor should reject URL 'null': FAIL (Chrome: PASS)
WebTransport constructor should reject URL '': FAIL (Chrome: PASS)
WebTransport constructor should reject URL 'no-scheme': FAIL (Chrome: PASS)
WebTransport constructor should reject URL 'http://example.com/': FAIL (Chrome: PASS)
WebTransport constructor should reject URL 'quic-transport://example.com/': FAIL (Chrome: PASS)
WebTransport constructor should reject URL 'https:///': FAIL (Chrome: PASS)
WebTransport constructor should reject URL 'https://example.com/#failing': FAIL (Chrome: PASS)
WebTransport constructor should reject URL 'https://web-platform.test:999999/': FAIL (Chrome: PASS)
Connection to port 0 should fail: FAIL (Chrome: FAIL)
/webtransport/constructor.any.worker.html
WebTransport constructor should reject URL 'null': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL '': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'no-scheme': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'http://example.com/': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'quic-transport://example.com/': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https:///': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https://example.com/#failing': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https://web-platform.test:999999/': FAIL (Chrome: PASS, Safari: FAIL)
Connection to port 0 should fail: FAIL (Chrome: FAIL, Safari: FAIL)
/webtransport/constructor.any.html
WebTransport constructor should reject URL 'null': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL '': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'no-scheme': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'http://example.com/': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'quic-transport://example.com/': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https:///': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https://example.com/#failing': FAIL (Chrome: PASS, Safari: FAIL)
WebTransport constructor should reject URL 'https://web-platform.test:999999/': FAIL (Chrome: PASS, Safari: FAIL)
Connection to port 0 should fail: FAIL (Chrome: FAIL, Safari: FAIL)
/webtransport/csp-fail.window.html
WebTransport connection should fail when CSP connect-src is set to none and reject the promises: FAIL (Chrome: PASS, Safari: FAIL)
/webtransport/csp-pass.window.html
WebTransport connection should succeed when CSP connect-src destination is set to the page: FAIL (Chrome: FAIL, Safari: FAIL)
/webtransport/datagrams.https.any.html
Datagrams are echoed successfully: FAIL (Safari: FAIL)
Sending and receiving datagrams is ready to use before session is established: FAIL (Safari: FAIL)
Datagram's outgoingHighWaterMark correctly regulates written datagrams: FAIL (Safari: FAIL)
Datagrams read is less than or equal to the incomingHighWaterMark: FAIL (Safari: FAIL)
/webtransport/datagrams.https.any.worker.html
Datagrams are echoed successfully: FAIL (Chrome: FAIL, Safari: FAIL)
Sending and receiving datagrams is ready to use before session is established: FAIL (Chrome: TIMEOUT, Safari: FAIL)
Datagram's outgoingHighWaterMark correctly regulates written datagrams: FAIL (Chrome: NOTRUN, Safari: FAIL)
Datagrams read is less than or equal to the incomingHighWaterMark: FAIL (Chrome: NOTRUN, Safari: FAIL)
/webtransport/datagrams.https.any.serviceworker.html
Datagrams are echoed successfully: FAIL (Safari: FAIL)
Sending and receiving datagrams is ready to use before session is established: FAIL (Safari: FAIL)
Datagram's outgoingHighWaterMark correctly regulates written datagrams: FAIL (Safari: FAIL)
Datagrams read is less than or equal to the incomingHighWaterMark: FAIL (Safari: FAIL)
/webtransport/datagrams.https.any.sharedworker.html
Datagrams are echoed successfully: FAIL (Chrome: FAIL)
Sending and receiving datagrams is ready to use before session is established: FAIL (Chrome: TIMEOUT)
Datagram's outgoingHighWaterMark correctly regulates written datagrams: FAIL (Chrome: NOTRUN)
Datagrams read is less than or equal to the incomingHighWaterMark: FAIL (Chrome: NOTRUN)
/webtransport/streams-echo.any.serviceworker.html
WebTransport server should be able to create and handle a bidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport server should be able to accept and handle a bidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport server should be able to create, accept, and handle a unidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
/webtransport/streams-echo.any.worker.html
WebTransport server should be able to create and handle a bidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport server should be able to accept and handle a bidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport server should be able to create, accept, and handle a unidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
/webtransport/streams-echo.any.sharedworker.html
WebTransport server should be able to create and handle a bidirectional stream: FAIL (Chrome: FAIL)
WebTransport server should be able to accept and handle a bidirectional stream: FAIL (Chrome: FAIL)
WebTransport server should be able to create, accept, and handle a unidirectional stream: FAIL (Chrome: FAIL)
/webtransport/streams-echo.any.html
WebTransport server should be able to create and handle a bidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport server should be able to accept and handle a bidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)
WebTransport server should be able to create, accept, and handle a unidirectional stream: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6b7fe465b548
[wpt PR 30996] - Add Datagrams WPTs for WebTransport, a=testonly
https://hg.mozilla.org/integration/autoland/rev/b4bc56ccef92
[wpt PR 30996] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/6b7fe465b548
https://hg.mozilla.org/mozilla-central/rev/b4bc56ccef92

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