WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
33409
websocket/tests/url-with-credential.html failed on Tiger Bot
https://bugs.webkit.org/show_bug.cgi?id=33409
Summary
websocket/tests/url-with-credential.html failed on Tiger Bot
Eric Seidel (no email)
Reported
2010-01-08 16:23:30 PST
websocket/tests/url-with-credential.html failed on Tiger Bot
http://build.webkit.org/results/Tiger%20Intel%20Release/r53017%20(7578)/results.html
--- layout-test-results/websocket/tests/url-with-credential-expected.txt 2010-01-08 15:59:34.000000000 -0800 +++ layout-test-results/websocket/tests/url-with-credential-actual.txt 2010-01-08 15:59:34.000000000 -0800 @@ -4,10 +4,9 @@ url=ws://user:
pass@127.0.0.1
:8880/websocket/tests/echo-location WebSocket is open -received:ws://127.0.0.1:8880/websocket/tests/echo-location WebSocket is closed PASS handshake_success is true -PASS ws_location is "ws://127.0.0.1:8880/websocket/tests/echo-location" +FAIL ws_location should be ws://127.0.0.1:8880/websocket/tests/echo-location (of type string). Was undefined (of type undefined). PASS successfullyParsed is true TEST COMPLETE "credential handing seems flaky with Tiger's NSURLConnection" -- Alexey This might be related to
bug 31412
which we just skipped. Alexey says this should be part of some expectations file eventually but for now we should probably just skip it. Unless someone would like to debug credential handling on Tiger? :)
Attachments
Add attachment
proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1
2010-01-08 16:27:50 PST
I misunderstood the issue at first, thought it was one of XHR credential tests, which have their reasons to be flaky on Tiger. This one should probably be investigated before skipping. Sorry for the confusion.
Eric Seidel (no email)
Comment 2
2010-01-09 19:29:48 PST
Another failure of this test tonight:
http://build.webkit.org/results/Tiger%20Intel%20Release/r53040%20(7594)/results.html
Fumitoshi Ukai
Comment 3
2010-02-08 22:14:39 PST
(In reply to
comment #0
)
> websocket/tests/url-with-credential.html failed on Tiger Bot > >
http://build.webkit.org/results/Tiger%20Intel%20Release/r53017%20(7578)/results.html
http://build.webkit.org/results/Tiger%20Intel%20Release/r53017%20(7578)/pywebsocket_log.txt
[2010-01-08 15:59:23,815] [CRITICAL] root: (48, 'Address already in use') corrent pywebsocket server didn't run.
> --- layout-test-results/websocket/tests/url-with-credential-expected.txt > 2010-01-08 15:59:34.000000000 -0800 > +++ layout-test-results/websocket/tests/url-with-credential-actual.txt > 2010-01-08 15:59:34.000000000 -0800 > @@ -4,10 +4,9 @@ > > url=ws://user:
pass@127.0.0.1
:8880/websocket/tests/echo-location > WebSocket is open > -received:ws://127.0.0.1:8880/websocket/tests/echo-location > WebSocket is closed > PASS handshake_success is true > -PASS ws_location is "ws://127.0.0.1:8880/websocket/tests/echo-location" > +FAIL ws_location should be ws://127.0.0.1:8880/websocket/tests/echo-location > (of type string). Was undefined (of type undefined). > PASS successfullyParsed is true > > TEST COMPLETE > > "credential handing seems flaky with Tiger's NSURLConnection" -- Alexey > > This might be related to
bug 31412
which we just skipped. > > Alexey says this should be part of some expectations file eventually but for > now we should probably just skip it. Unless someone would like to debug > credential handling on Tiger? :)
Fumitoshi Ukai
Comment 4
2010-02-08 22:16:14 PST
(In reply to
comment #2
)
> Another failure of this test tonight: >
http://build.webkit.org/results/Tiger%20Intel%20Release/r53040%20(7594)/results.html
http://build.webkit.org/results/Tiger%20Intel%20Release/r53040%20(7594)/pywebsocket_log.txt
same as
r53017
(7578)
Eric Seidel (no email)
Comment 5
2010-09-30 11:04:23 PDT
We don't run a Tiger bot anymore.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug