Bug 215185 – [ iOS wk2 Release ] imported/w3c/web-platform-tests/IndexedDB/structured-clone-transaction-state.any.worker.html is a flaky failure

• Component: New Bugs
• Status: RESOLVED DUPLICATE

[Hector Lopez]

imported/w3c/web-platform-tests/IndexedDB/structured-clone-transaction-state.any.worker.html

This test is a flaky failure on iOS wk2 Release on iPhoneSE Simulator. The first occurrence of a failure is at r263762.

History:
https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2FIndexedDB%2Fstructured-clone-transaction-state.any.worker.html&limit=50000&platform=ios&style=release&model=iPhone%20SE

Diff:
--- /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/IndexedDB/structured-clone-transaction-state.any.worker-expected.txt
+++ /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/IndexedDB/structured-clone-transaction-state.any.worker-actual.txt
@@ -1,11 +1,4 @@
 
-FAIL Transaction inactive during structured clone in IDBObjectStore.add() assert_throws_dom: transaction should not be active during structured clone function "() => {
-        objectStore.get('key');
-      }" did not throw
-FAIL Transaction inactive during structured clone in IDBObjectStore.put() assert_throws_dom: transaction should not be active during structured clone function "() => {
-        objectStore.get('key');
-      }" did not throw
-FAIL Transaction inactive during structured clone in IDBCursor.update() assert_throws_dom: transaction should not be active during structured clone function "() => {
-        objectStore.get('key');
-      }" did not throw
+Harness Error (TIMEOUT), message = null
 
+

[Radar WebKit Bug Importer]

<rdar://problem/66588216>

[Hector Lopez]

Test expectation added while investigated:

https://trac.webkit.org/changeset/265300/webkit

[Sihui Liu]

Expectations updated at https://bugs.webkit.org/show_bug.cgi?id=228241 as the test is no longer flaky.

*** This bug has been marked as a duplicate of bug 228241 ***