231337 2021-10-06 16:11:42 -0700 [ iOS 15 Debug ] imported/w3c/web-platform-tests/xhr/send-timeout-events.htm is a flaky failure 2021-11-04 10:19:46 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build iPhone / iPad Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=150806 InRadar P2 Normal --- 1 ayumi_kojima webkit-unassigned aakash_jain jbedard repstein webkit-bot-watchers-bugzilla webkit-bug-importer youennf oldest_to_newest 1801401 0 ayumi_kojima 2021-10-06 16:11:42 -0700 imported/w3c/web-platform-tests/xhr/send-timeout-events.htm Is flaky failing on iOS 15 Debug. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fxhr%2Fsend-timeout-events.htm Diff: --- /Volumes/Data/worker/ios-simulator-15-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/xhr/send-timeout-events-expected.txt +++ /Volumes/Data/worker/ios-simulator-15-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/xhr/send-timeout-events-actual.txt @@ -1,3 +1,3 @@ -PASS XMLHttpRequest: The send() method: timeout is not 0 +FAIL XMLHttpRequest: The send() method: timeout is not 0 assert_equals: expected 0 but got 857098 1801402 1 webkit-bug-importer 2021-10-06 16:12:42 -0700 <rdar://problem/83956855> 1801403 2 ayumi_kojima 2021-10-06 16:16:20 -0700 Marked test expectations https://trac.webkit.org/changeset/283677/webkit 1806850 3 ayumi_kojima 2021-10-20 14:37:36 -0700 I was able to reproduce the failure locally on iOS 15 using run-webkit-tests --force --iterations 500 --exit-after-n-failures 1 --debug imported/w3c/web-platform-tests/xhr/send-timeout-events.htm --ios-simulator --no-timeout. The test failed with r269120 and passed with r269118 (r269119 is not available to test). 1807142 4 jbedard 2021-10-21 08:03:04 -0700 (In reply to ayumi_kojima from comment #3) > I was able to reproduce the failure locally on iOS 15 using run-webkit-tests > --force --iterations 500 --exit-after-n-failures 1 --debug > imported/w3c/web-platform-tests/xhr/send-timeout-events.htm --ios-simulator > --no-timeout. > > The test failed with r269120 and passed with r269118 (r269119 is not > available to test). r269120 definitely can't cause a layout test failure like this, it didn't actually change anything about the binary you're testing. 1811572 5 ayumi_kojima 2021-11-03 12:02:19 -0700 I worked on reproduction again just to make sure. Test failed with r269121 and r269120 and passed with r269118 and r269117. So most likely it is either r269120 or r269119. 1811579 6 ryanhaddad 2021-11-03 12:11:24 -0700 r269119 was a change on a branch, so it couldn't have affected trunk. r269120 was a rename of a directory used by buildbot, so it is also unlikely to have impacted test results. In spite of the reproduction, I still find this hard to believe.