Bug 232483

Summary: [ iOS ] storage/filesystemaccess/sync-access-handle-basics-worker.html is failing
Product: WebKit Reporter: ayumi_kojima
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: sihui_liu, webkit-bot-watchers-bugzilla, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: iPhone / iPad   
OS: Unspecified   

ayumi_kojima
Reported 2021-10-29 08:16:57 PDT
storage/filesystemaccess/sync-access-handle-basics-worker.html Is constantly failing on iOS 15. History: https://results.webkit.org/?suite=layout-tests&test=storage%2Ffilesystemaccess%2Fsync-access-handle-basics-worker.html Result page: https://build.webkit.org/results/Apple-iPadOS-15-Simulator-Debug-WK2-Tests/r285017%20(182)/results.html Diff: --- /Volumes/Data/worker/ipados-simulator-15-debug-tests-wk2/build/layout-test-results/storage/filesystemaccess/sync-access-handle-basics-worker-expected.txt +++ /Volumes/Data/worker/ipados-simulator-15-debug-tests-wk2/build/layout-test-results/storage/filesystemaccess/sync-access-handle-basics-worker-actual.txt @@ -4,15 +4,9 @@ Starting worker: resources/sync-access-handle-basics.js -PASS [Worker] fileHandle.name is "sync-access-handle.txt" -PASS [Worker] fileHandle.kind is "file" -[Worker] accessHandle1 is created -PASS [Worker] size is 0 -[Worker] accessHandle2 cannot be created -PASS [Worker] createError.toString() is "InvalidStateError: The object is in an invalid state." -[Worker] accessHandle1 is closed -[Worker] accessHandle2 is created +FAIL [Worker] TypeError: Type error PASS successfullyParsed is true +Some tests failed. TEST COMPLETE
Attachments
Radar WebKit Bug Importer
Comment 1 2021-10-29 08:17:19 PDT
ayumi_kojima
Comment 2 2021-10-29 08:17:45 PDT
According to the history, it looks like the failure started at https://trac.webkit.org/changeset/285007/webkit
ayumi_kojima
Comment 3 2021-10-29 08:48:30 PDT
Alexey Proskuryakov
Comment 4 2021-11-01 09:13:17 PDT
Marking as fixed per the above.
Note You need to log in before you can comment on or make changes to this bug.