NEW 227877
[ BigSur release ]imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=227877
Summary [ BigSur release ]imported/w3c/web-platform-tests/navigation-timing/test_timi...
Eric Hutchison
Reported 2021-07-12 10:32:00 PDT
imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order.html is a flaky failure. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fnavigation-timing%2Ftest_timing_attributes_order.html&platform=mac Diff: --- /Volumes/Data/worker/bigsur-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order-expected.txt +++ /Volumes/Data/worker/bigsur-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order-actual.txt @@ -26,14 +26,14 @@ PASS window.performance.timing.domainLookupStart >= window.performance.timing.fetchStart PASS window.performance.timing.domainLookupStart difference with window.performance.timing.fetchStart is 0 or at least 5 microseconds PASS window.performance.timing.domainLookupEnd > 0 -PASS window.performance.timing.domainLookupEnd >= window.performance.timing.domainLookupStart +FAIL window.performance.timing.domainLookupEnd >= window.performance.timing.domainLookupStart assert_true: window.performance.timing.domainLookupEnd >= window.performance.timing.domainLookupStart expected true got false PASS window.performance.timing.domainLookupEnd difference with window.performance.timing.domainLookupStart is 0 or at least 5 microseconds PASS window.performance.timing.connectStart > 0 PASS window.performance.timing.connectStart >= window.performance.timing.domainLookupEnd PASS window.performance.timing.connectStart difference with window.performance.timing.domainLookupEnd is 0 or at least 5 microseconds PASS window.performance.timing.connectEnd > 0 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 +FAIL window.performance.timing.connectEnd difference with window.performance.timing.connectStart is 0 or at least 5 microseconds assert_true: window.performance.timing.connectEnd difference with window.performance.timing.connectStart is 0 or at least 5 microseconds expected true got false 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
Attachments
Update Test Expectations (2.13 KB, patch)
2021-07-12 13:42 PDT, Eric Hutchison
ews-feeder: commit-queue-
Radar WebKit Bug Importer
Comment 1 2021-07-12 10:33:18 PDT
Eric Hutchison
Comment 2 2021-07-12 10:57:21 PDT
Reproduced failure on r279826 using: run-webkit-tests --iterations 500 --exit-after-n-failures 2 -f imported/w3c/web-platform-tests/navigation-timing/test_timing_attributes_order.html. Reproduced on r279803 with same command as above. This was the earliest revision that I reproduced the issue.
Eric Hutchison
Comment 3 2021-07-12 13:42:53 PDT
Created attachment 433351 [details] Update Test Expectations
Truitt Savell
Comment 4 2021-07-12 13:46:06 PDT
Comment on attachment 433351 [details] Update Test Expectations Clearing flags on attachment: 433351 Committed r279848 (239603@main): <https://commits.webkit.org/239603@main>
Note You need to log in before you can comment on or make changes to this bug.