Bug 220484

Summary: [Mojave] imported/w3c/web-platform-tests/html/semantics/document-metadata/the-meta-element/pragma-directives/attr-meta-http-equiv-refresh/parsing.html is a flaky failure
Product: WebKit Reporter: Ryan Haddad <ryanhaddad>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=220230

Ryan Haddad
Reported 2021-01-08 14:38:49 PST
imported/w3c/web-platform-tests/html/semantics/document-metadata/the-meta-element/pragma-directives/attr-meta-http-equiv-refresh/parsing.html is a flaky failure on Mojave --- /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/document-metadata/the-meta-element/pragma-directives/attr-meta-http-equiv-refresh/parsing-expected.txt +++ /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/document-metadata/the-meta-element/pragma-directives/attr-meta-http-equiv-refresh/parsing-actual.txt @@ -1,3 +1,5 @@ + +Harness Error (TIMEOUT), message = null PASS <meta>: "" PASS Refresh header: "" @@ -120,7 +122,7 @@ PASS Refresh header: ".9; url=foo" PASS <meta>: "0.9; url=foo" PASS Refresh header: "0.9; url=foo" -PASS <meta>: "0...9; url=foo" +TIMEOUT <meta>: "0...9; url=foo" Test timed out PASS Refresh header: "0...9; url=foo" PASS <meta>: "0...; url=foo" PASS Refresh header: "0...; url=foo" https://results.webkit.org/?suite=layout-tests&test=imported/w3c/web-platform-tests/html/semantics/document-metadata/the-meta-element/pragma-directives/attr-meta-http-equiv-refresh/parsing.html&recent=false
Attachments
Ryan Haddad
Comment 1 2021-01-08 14:43:14 PST
Marked as flaky in r271323 to help speed up EWS + CQ.
Radar WebKit Bug Importer
Comment 2 2021-01-15 14:39:20 PST
Ryan Haddad
Comment 3 2021-01-20 15:43:11 PST
The test was consistently failing until it was rebaselined in https://trac.webkit.org/changeset/269247/webkit, but it was still marked as failing until it was modified again in https://trac.webkit.org/changeset/271142/webkit.
Ryan Haddad
Comment 4 2021-01-20 15:44:45 PST
I think this has been flaky for quite a long time, it just wasn't noticed because of the consistent failure, then started showing up once the failure expectation was removed.
Note You need to log in before you can comment on or make changes to this bug.