Bug 206687

Summary: [iOS] imported/w3c/web-platform-tests/beacon/idlharness.any.html is flakey and timing out.
Product: WebKit Reporter: Jason Lawrence <Lawrence.j>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: cdumez, ryanhaddad, tsavell, webkit-bot-watchers-bugzilla, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Update Test Expectations none

Jason Lawrence
Reported 2020-01-23 11:31:24 PST
imported/w3c/web-platform-tests/beacon/idlharness.any.html Description: The test is flakey and timing out. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fbeacon%2Fidlharness.any.html Diff: I was not able to locate a diff for this test.
Attachments
Update Test Expectations (1.42 KB, patch)
2020-01-28 09:08 PST, Jason Lawrence
no flags
Radar WebKit Bug Importer
Comment 1 2020-01-23 11:31:55 PST
Ryan Haddad
Comment 2 2020-01-23 13:38:13 PST
This test appears to have been flaky since it was imported as part of https://trac.webkit.org/changeset/253760/webkit
Alexey Proskuryakov
Comment 3 2020-01-26 13:24:59 PST
It would be so useful to see what this test does. But this is its whole content: <!-- This file is required for WebKit test infrastructure to run the templated test --
Chris Dumez
Comment 4 2020-01-26 17:38:23 PST
(In reply to Alexey Proskuryakov from comment #3) > It would be so useful to see what this test does. But this is its whole > content: > > <!-- This file is required for WebKit test infrastructure to run the > templated test -- You need to look at the .js, not the .html in this case.
Jason Lawrence
Comment 5 2020-01-28 09:08:32 PST
Created attachment 389013 [details] Update Test Expectations
Truitt Savell
Comment 6 2020-01-28 09:15:54 PST
Comment on attachment 389013 [details] Update Test Expectations Clearing flags on attachment: 389013 Committed r255245: <https://trac.webkit.org/changeset/255245>
Note You need to log in before you can comment on or make changes to this bug.