Bug 163139

Summary: [mac-wk2] LayoutTest http/tests/loading/basic-auth-load-URL-with-consecutive-slashes.html is a flaky failure
Product: WebKit Reporter: Ryan Haddad <ryanhaddad>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, dbates, Hironori.Fujii
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=222563

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.
Comment 3 Fujii Hironori 2023-11-20 12:11:36 PST

*** This bug has been marked as a duplicate of bug 222563 ***