RESOLVED FIXED Bug 240033
REGRESSION(r293671): [ iOS ] 2 TestWebKitAPI.MediaLoading.RangeRequestSynthesis (API-Tests) are constant failures
https://bugs.webkit.org/show_bug.cgi?id=240033
Summary REGRESSION(r293671): [ iOS ] 2 TestWebKitAPI.MediaLoading.RangeRequestSynthes...
Robert Jenner
Reported 2022-05-03 13:25:27 PDT
The following two TestWebKitAPI.MediaLoading.RangeRequestSynthesis API-Tests are constant failures on iOS15: TestWebKitAPI.MediaLoading.RangeRequestSynthesisWithContentLength TestWebKitAPI.MediaLoading.RangeRequestSynthesisWithoutContentLength HISTORY: https://results.webkit.org/?suite=api-tests&suite=api-tests&test=TestWebKitAPI.MediaLoading.RangeRequestSynthesisWithContentLength&test=TestWebKitAPI.MediaLoading.RangeRequestSynthesisWithoutContentLength FAILURES: TestWebKitAPI.MediaLoading.RangeRequestSynthesisWithContentLength File name unavailable Unknown C++ exception thrown in the test body. TestWebKitAPI.MediaLoading.RangeRequestSynthesisWithoutContentLength File name unavailable Unknown C++ exception thrown in the test body.
Attachments
Radar WebKit Bug Importer
Comment 1 2022-05-03 13:25:45 PDT
Robert Jenner
Comment 2 2022-05-03 14:22:17 PDT
I was able to reproduce the failure at iOS-15 Debug ToT using the following test: run-api-tests <test goes here> I was also able to verify a regression point. The failure was reproducible back to r293671, and it was not reproducible at r293670. So it appears that https://commits.webkit.org/250173@main introduced this failure.
Robert Jenner
Comment 3 2022-05-03 16:43:43 PDT
Robert Jenner
Comment 4 2022-05-04 14:32:11 PDT
EWS
Comment 5 2022-05-04 16:15:30 PDT
Test gardening commit r293798 (250272@main): <https://commits.webkit.org/250272@main> Reviewed commits have been landed. Closing PR #502 and removing active labels.
Eric Carlson
Comment 6 2022-05-20 12:49:30 PDT
EWS
Comment 7 2022-05-23 11:17:38 PDT
Committed r294658 (250879@main): <https://commits.webkit.org/250879@main> Reviewed commits have been landed. Closing PR #846 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.