Bug 163139 - [mac-wk2] LayoutTest http/tests/loading/basic-auth-load-URL-with-consecutive-slashes.html is a flaky failure
Summary: [mac-wk2] LayoutTest http/tests/loading/basic-auth-load-URL-with-consecutive-...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-07 12:42 PDT by Ryan Haddad
Modified: 2021-03-01 13:39 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2016-10-07 12:42:56 PDT
LayoutTest http/tests/loading/basic-auth-load-URL-with-consecutive-slashes.html is a flaky failure

https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/builds/8647

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2Floading%2Fbasic-auth-load-URL-with-consecutive-slashes.html

--- /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/http/tests/loading/basic-auth-load-URL-with-consecutive-slashes-expected.txt
+++ /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/http/tests/loading/basic-auth-load-URL-with-consecutive-slashes-actual.txt
@@ -1,8 +1,8 @@
 main frame - didStartProvisionalLoadForFrame
 main frame - didCommitLoadForFrame
 frame "frame" - didStartProvisionalLoadForFrame
+127.0.0.1:8000 - didReceiveAuthenticationChallenge - Responding with webkit:rocks
 main frame - didFinishDocumentLoadForFrame
-127.0.0.1:8000 - didReceiveAuthenticationChallenge - Responding with webkit:rocks
 frame "frame" - didCommitLoadForFrame
 frame "frame" - didFinishDocumentLoadForFrame
 frame "frame" - willPerformClientRedirectToURL: http://127.0.0.1:8000/a//b/non-existent-file.html
Comment 1 Ryan Haddad 2016-10-07 12:46:48 PDT
Marked test as flaky in http://trac.webkit.org/projects/webkit/changeset/206927
Comment 2 Alexey Proskuryakov 2016-11-15 11:45:07 PST
This looks like a bug in the test, where it doesn't wait for main frame load to finish.