[wpt-sync] Sync PR 54412 - Await calls to `configureServer` in DBSC WPTs
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox144 fixed)
| Tracking | Status | |
|---|---|---|
| firefox144 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 54412 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/54412
Details from upstream follow.
thefrog <thefrog@chromium.org> wrote:
Await calls to
configureServerin DBSC WPTs
configureServeris async, so calls to it should be awaited.Change-Id: Iaa3f975582ec8348c183771b5297daa636d4fff2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6858412
Commit-Queue: thefrog \<thefrog@chromium.org>
Reviewed-by: Daniel Rubery \<drubery@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1503608}
| Assignee | ||
Comment 1•7 months ago
|
||
| Assignee | ||
Comment 2•7 months ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 16 tests and 1 subtests
Status Summary
Firefox
TIMEOUT: 32
NOTRUN : 19
Chrome
TIMEOUT: 32
NOTRUN : 19
Safari
TIMEOUT: 32
NOTRUN : 19
Links
Details
New Tests That Don't Pass
- /device-bound-session-credentials/allowed-refresh-initiators.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- An established session refreshes when initated by the owning site:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - An established session refreshes when initated by a host in allowed_refresh_initiators:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - An established session does not refresh when initated by a host not in allowed_refresh_initiators:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- An established session refreshes when initated by the owning site:
- /device-bound-session-credentials/credentials-matching.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Expires attribute in credentials doesn't affect matching:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - Max-Age attribute in credentials doesn't affect matching:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - HttpOnly attribute in credentials affects matching:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - SameSite attribute in credentials affects matching:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - Secure attribute in credentials affects matching:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - Path attribute in credentials affects matching:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - Partition attribute in credentials affects matching:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- Expires attribute in credentials doesn't affect matching:
- /device-bound-session-credentials/debug-header.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- A session that fails to reach the refresh endpoint sets debug header:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - Same-site redirects continue to send debug header:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - Cross-site redirects do not send debug header:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - Two failing sessions both set debug header:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- A session that fails to reach the refresh endpoint sets debug header:
- /device-bound-session-credentials/include-site.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- An established session refreshes across origins if the site is included:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - An established session does not refresh across origins if the site is not included:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- An established session refreshes across origins if the site is included:
- /device-bound-session-credentials/multiple-credentials.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- A session can have multiple credentials set:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- A session can have multiple credentials set:
- /device-bound-session-credentials/multiple-registrations.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Multiple registrations can be triggered in one response (single header):
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - Multiple registrations can be triggered in one response (multiple headers):
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- Multiple registrations can be triggered in one response (single header):
- /device-bound-session-credentials/refresh-does-not-send-challenge.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Refresh does not send back Sec-Session-Challenge:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- Refresh does not send back Sec-Session-Challenge:
- /device-bound-session-credentials/refresh-replaces-config.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Refresh can replace session config:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - Refresh cannot replace session identifier:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- Refresh can replace session config:
- /device-bound-session-credentials/refresh-with-continue-false.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- A session ended with continue:false does not refresh cookies:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- A session ended with continue:false does not refresh cookies:
- /device-bound-session-credentials/registration-sends-challenge.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Registration can send back Sec-Session-Challenge:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- Registration can send back Sec-Session-Challenge:
- /device-bound-session-credentials/resolving-urls.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- The registration and refresh endpoints can be configured as absolute URLs:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - The registration and refresh endpoints can be configured as relative URLs with leading slash:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - The registration and refresh endpoints can be configured as relative URLs without leading slash:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- The registration and refresh endpoints can be configured as absolute URLs:
- /device-bound-session-credentials/session-cookie-has-no-attributes.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- An established session can refresh a cookie that has all default attributes:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- An established session can refresh a cookie that has all default attributes:
- /device-bound-session-credentials/set-authorization.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Session registration sends the authorization value:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- Session registration sends the authorization value:
- /device-bound-session-credentials/set-early-challenge.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- A challenge can be set ahead of time:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - A challenge can be set for multiple sessions ahead of time (single header):
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - A challenge can be set for multiple sessions ahead of time (multiple headers):
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- A challenge can be set ahead of time:
- /device-bound-session-credentials/set-scope-origin.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- A request within the scope origin refreshes:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT) - A request outside the scope origin does not refresh:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- A request within the scope origin refreshes:
- /device-bound-session-credentials/set-scope-specification.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- Scope specification configuration is respected:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)
- Scope specification configuration is respected:
Description
•