Closed
Bug 1879030
Opened 5 months ago
Closed 1 month ago
New wpt failures in /fetch/content-encoding/zstd/ [bad-zstd-body.https.any.sharedworker.html, bad-zstd-body.https.any.html, bad-zstd-body.https.any.worker.html, and 13 others]
Categories
(Core :: DOM: Networking, defect)
Core
DOM: Networking
Tracking
()
RESOLVED
FIXED
126 Branch
Tracking | Status | |
---|---|---|
firefox126 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
Details
(Whiteboard: [wpt])
Syncing wpt PR 44393 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
- /fetch/content-encoding/zstd/bad-zstd-body.https.any.sharedworker.html [wpt.fyi]
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with blob() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with json() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with text() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
- /fetch/content-encoding/zstd/bad-zstd-body.https.any.html [wpt.fyi]
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with blob() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with json() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with text() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
- /fetch/content-encoding/zstd/bad-zstd-body.https.any.worker.html [wpt.fyi]
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with blob() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with json() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with text() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
- /fetch/content-encoding/zstd/bad-zstd-body.https.any.serviceworker.html [wpt.fyi]
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with blob() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with json() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
) - Consuming the body of a resource with bad zstd content with text() should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with bad zstd content with arrayBuffer() should reject:
- /fetch/content-encoding/zstd/big-window-zstd-body.tentative.https.any.worker.html [wpt.fyi]
- Consuming the body of a resource with too large of a zstd window size should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with too large of a zstd window size should reject:
- /fetch/content-encoding/zstd/big-window-zstd-body.tentative.https.any.html [wpt.fyi]
- Consuming the body of a resource with too large of a zstd window size should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with too large of a zstd window size should reject:
- /fetch/content-encoding/zstd/big-window-zstd-body.tentative.https.any.sharedworker.html [wpt.fyi]
- Consuming the body of a resource with too large of a zstd window size should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with too large of a zstd window size should reject:
- /fetch/content-encoding/zstd/big-window-zstd-body.tentative.https.any.serviceworker.html [wpt.fyi]
- Consuming the body of a resource with too large of a zstd window size should reject:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Consuming the body of a resource with too large of a zstd window size should reject:
- /fetch/content-encoding/zstd/big-zstd-body.https.any.html [wpt.fyi]
- large zstd data should be decompressed successfully:
FAIL
(Chrome:PASS
, Safari:FAIL
) - large zstd data should be decompressed successfully with byte stream:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- large zstd data should be decompressed successfully:
- /fetch/content-encoding/zstd/big-zstd-body.https.any.sharedworker.html [wpt.fyi]
- large zstd data should be decompressed successfully:
FAIL
(Chrome:PASS
, Safari:FAIL
) - large zstd data should be decompressed successfully with byte stream:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- large zstd data should be decompressed successfully:
- /fetch/content-encoding/zstd/big-zstd-body.https.any.serviceworker.html [wpt.fyi]
- large zstd data should be decompressed successfully:
FAIL
(Chrome:PASS
, Safari:FAIL
) - large zstd data should be decompressed successfully with byte stream:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- large zstd data should be decompressed successfully:
- /fetch/content-encoding/zstd/big-zstd-body.https.any.worker.html [wpt.fyi]
- large zstd data should be decompressed successfully:
FAIL
(Chrome:PASS
, Safari:FAIL
) - large zstd data should be decompressed successfully with byte stream:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- large zstd data should be decompressed successfully:
- /fetch/content-encoding/zstd/zstd-body.https.any.sharedworker.html [wpt.fyi]
- fetched zstd data with content type text should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
) - fetched zstd data with content type octetstream should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- fetched zstd data with content type text should be decompressed.:
- /fetch/content-encoding/zstd/zstd-body.https.any.worker.html [wpt.fyi]
- fetched zstd data with content type text should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
) - fetched zstd data with content type octetstream should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- fetched zstd data with content type text should be decompressed.:
- /fetch/content-encoding/zstd/zstd-body.https.any.html [wpt.fyi]
- fetched zstd data with content type text should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
) - fetched zstd data with content type octetstream should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- fetched zstd data with content type text should be decompressed.:
- /fetch/content-encoding/zstd/zstd-body.https.any.serviceworker.html [wpt.fyi]
- fetched zstd data with content type text should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
) - fetched zstd data with content type octetstream should be decompressed.:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- fetched zstd data with content type text should be decompressed.:
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1878596 lands.
Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.
This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/
If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.
Comment 1•1 month ago
•
|
||
Fixed by bug 1871963
Blocks: zstd
Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox126:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 126 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•