Bug 160368

Summary:

[ios-sim] LayoutTest http/tests/xmlhttprequest/workers/methods-async.html is a flaky timeout

Product:

WebKit

Reporter:

Ryan Haddad <ryanhaddad>

Component:

New Bugs

Assignee:

Matt Lewis <jlewis3>

Status:

NEW

Severity:

Normal

CC:

jlewis3

Priority:

Version:

WebKit Nightly Build

Hardware:

Unspecified

OS:

Unspecified

See Also:

https://bugs.webkit.org/show_bug.cgi?id=142912
https://bugs.webkit.org/show_bug.cgi?id=143403
https://bugs.webkit.org/show_bug.cgi?id=151455

Attachments:

Description	Flags
Mark test as flaky	none

Ryan Haddad

Reported 2016-07-29 17:53:12 PDT

[ios-sim] LayoutTest http/tests/xmlhttprequest/workers/methods-async.html is a flaky timeout https://build.webkit.org/results/Apple%20iOS%209%20Simulator%20Release%20WK2%20(Tests)/r203928%20(7774)/results.html https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2Fxmlhttprequest%2Fworkers%2Fmethods-async.html

Attachments
Mark test as flaky (1.47 KB, patch) 2017-05-04 12:25 PDT, Matt Lewis	no flags	Details Formatted Diff Diff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.

Ryan Haddad

Comment 1 2016-07-29 17:55:39 PDT

Marked as flaky in http://trac.webkit.org/projects/webkit/changeset/203934

Ryan Haddad

Comment 2 2016-07-29 17:57:20 PDT

Actually, this may be a bot-specific issue.

Ryan Haddad

Comment 3 2016-07-29 17:58:30 PDT

(In reply to comment #2) > Actually, this may be a bot-specific issue. Rebooted the bot in question, will monitor flakiness dashboard to see if this is still an issue.

Matt Lewis

Comment 4 2017-05-04 12:24:29 PDT

The test appears to be flaky on debug as well and does not seem to be bot related.

Matt Lewis

Comment 5 2017-05-04 12:25:55 PDT

Created attachment 309084 [details] Mark test as flaky

Ryan Haddad

Comment 6 2017-05-04 13:20:37 PDT

Comment on attachment 309084 [details] Mark test as flaky Clearing flags on attachment: 309084 Committed r216205: <http://trac.webkit.org/changeset/216205>

Note You need to log in before you can comment on or make changes to this bug.