Bug 232316

Summary: [ macOS ] imported/w3c/web-platform-tests/hr-time/basic.html is a flaky failure
Product: WebKit Reporter: ayumi_kojima
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: webkit-bot-watchers-bugzilla, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

ayumi_kojima
Reported 2021-10-26 10:25:29 PDT
imported/w3c/web-platform-tests/hr-time/basic.html Is a flaky failure on macOS. History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fforms%2Fform-submission-crash-3.html Result page: https://build.webkit.org/results/Apple-BigSur-Debug-AppleSilicon-WK1-Tests/r284863%20(4244)/results.html Diff: --- /Volumes/Data/worker/bigsur-debug-applesilicon-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/hr-time/basic-expected.txt +++ /Volumes/Data/worker/bigsur-debug-applesilicon-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/hr-time/basic-actual.txt @@ -7,5 +7,5 @@ PASS High Resolution Time extension to the Performance interface PASS window.performance.now() function PASS window.performance.now() returns a number -PASS High resolution time has approximately the right relative magnitude +FAIL High resolution time has approximately the right relative magnitude assert_approx_equals: High resolution time value increased by approximately the same amount as time from date object expected 2057 +/- 30 but got 2015
Attachments
Radar WebKit Bug Importer
Comment 1 2021-10-26 10:25:49 PDT
ayumi_kojima
Comment 3 2021-10-26 11:33:58 PDT
I was not able to reproduce the failure locally using run-webkit-tests debugToTest -1 --iterations 500 --exit-after-n-failures 1 imported/w3c/web-platform-tests/hr-time/basic.html
ayumi_kojima
Comment 4 2021-10-26 11:38:18 PDT
It looks like the test has been flaky for at least 2 month with failing at this build https://build.webkit.org/#/builders/33/builds/3954
ayumi_kojima
Comment 5 2021-10-26 11:44:51 PDT
Note You need to log in before you can comment on or make changes to this bug.