209446 2020-03-23 16:05:59 -0700 [ Mac Debug and iOS ] imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order.html is flaky failing. 2021-07-12 11:25:41 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Mac macOS 10.14 RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 Lawrence.j webkit-unassigned tsavell webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 1633097 0 Lawrence.j 2020-03-23 16:05:59 -0700 imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order.html Description: This test is flaky failing on Mac Debug. It also flaky failing on iOS Debug and Release. The earliest visible failure is on 1/31/2020. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fnavigation-timing%2Ftest_timing_attributes_order.html&style=release&style=debug&platform=ios&platform=mac#recent=false Diff: --- /Volumes/Data/slave/catalina-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order-expected.txt +++ /Volumes/Data/slave/catalina-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order-actual.txt @@ -35,8 +35,8 @@ PASS window.performance.timing.connectEnd >= window.performance.timing.connectStart PASS window.performance.timing.connectEnd difference with window.performance.timing.connectStart is 0 or at least 5 microseconds PASS window.performance.timing.requestStart > 0 -PASS window.performance.timing.requestStart >= window.performance.timing.connectEnd -PASS window.performance.timing.requestStart difference with window.performance.timing.connectEnd is 0 or at least 5 microseconds +FAIL window.performance.timing.requestStart >= window.performance.timing.connectEnd assert_true: window.performance.timing.requestStart >= window.performance.timing.connectEnd expected true got false +FAIL window.performance.timing.requestStart difference with window.performance.timing.connectEnd is 0 or at least 5 microseconds assert_true: window.performance.timing.requestStart difference with window.performance.timing.connectEnd is 0 or at least 5 microseconds expected true got false PASS window.performance.timing.responseStart > 0 PASS window.performance.timing.responseStart >= window.performance.timing.requestStart PASS window.performance.timing.responseStart difference with window.performance.timing.requestStart is 0 or at least 5 microseconds 1633098 1 webkit-bug-importer 2020-03-23 16:07:00 -0700 <rdar://problem/60797221> 1633106 2 Lawrence.j 2020-03-23 16:19:32 -0700 I have marked this test as failing while this issue is investigated. https://trac.webkit.org/changeset/258885/webkit 1633110 3 Lawrence.j 2020-03-23 16:20:39 -0700 I was able to reproduce this issue with r258803 by running the command below. --debug --iterations 1000 --exit-after-n-failures 3 --force imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order.html 1776385 4 tsavell 2021-07-12 11:25:41 -0700 The failure mode of this test has changed. tracking the new failure mode in https://bugs.webkit.org/show_bug.cgi?id=227877