157916 2016-05-19 13:11:47 -0700 http/tests/misc/slow-loading-animated-image.html is flaky on iOS simulator and Windows 2017-09-01 15:02:40 -0700 1 1 1 Unclassified WebKit Tools / Tests Other Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=157500 P2 Normal --- 1 ap webkit-unassigned lforschler pvollan ryanhaddad sabouhallawa oldest_to_newest 1194894 0 ap 2016-05-19 13:11:47 -0700 http/tests/misc/slow-loading-animated-image.html fails very often on iOS Simulator, especially in debug: http://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2Fmisc%2Fslow-loading-animated-image.html 1194986 1 sabouhallawa 2016-05-19 14:59:38 -0700 The animated GIF used by this tests has 48 frames. Frames (1-47) have frame-length=20ms. Frame 48 has frame-length=10s. The test relies on capturing the 48th frame which should be shown after 47*20=940ms. On the mac ports, setTimeout for 1 second was enough to ensure the 48th frame is displayed at the time the test ends. For iOS, 1 second was not enough, so I had to increase the setTimeout from 1 second to 1500ms. This seems to be not enough all the times. I checked the flakiness dashboard and I found out the number of frames, which were animated after 1500ms, was: 16, 17, 20, 22, 23, 47. So increasing the setTimeout seems not an option. We have to wait at least 4500ms to ensure the first 47 frames were already rendered and the 48th frame is displayed. Other possible ways to fix this are the following: 1. Skip the test for iOS. 2. Add an internal API which returns the number of frames of an animated image and compare it with the actual number of frames the image has which is 48 for this test. 1195056 2 ap 2016-05-19 17:43:03 -0700 > 2. Add an internal API which returns the number of frames of an animated image and compare it with the actual number of frames the image has which is 48 for this test. This definitely sounds better than skipping. 1197789 3 ap 2016-05-31 09:19:08 -0700 Said, do you expect to work on this soon? The test fails on bots very frequently. 1199734 4 ryanhaddad 2016-06-06 15:32:52 -0700 Marked test as flaky in <http://trac.webkit.org/projects/webkit/changeset/201731>