-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PhoenixTests crash with internal URLSession error #10
Comments
This has happened locally on my MacBook Pro and when using GitHub Actions. |
This is the call-site where the error output happens: https://github.com/apple/swift/blob/164ebbf0e43916285a9cb19a7d68253fb7ba57b6/stdlib/public/Darwin/Foundation/URLSession.swift#L46 |
This reproduced on my MacBook Pro just now. I gathered all system state and will try to catch this tomorrow. |
I haven't seen this one in a while. I'll keep it open, however, because it's always been rare. |
This happened a few times yesterday and today. Most recently, it happened with |
It happened today. I wonder if I misread the previous crash log. Maybe it happens in
|
The crash just happened again. It again came from our friend
|
Ok, so, maybe it's not as straightforward as we had hoped. Another crash while running the tests.
|
@atdrendel they are both related to closing... |
I've got Charles working correctly with our Phoenix WebSockets. I'm going to run our tests in a loop until they fail in an attempt to catch the exception and the input causing it. Running tests in a loop:
Update I ran # generate the Xcode project file
swift package generate-xcodeproj
# run the tests in a loop
while xcodebuild test -project Phoenix.xcodeproj -scheme Phoenix-Package; do :; done |
I managed to reproduce the crash while proxying the WebSocket traffic. Based on what I saw, the traffic was normal, as were the "requests" made before it. Here's the information I captured during the crash. Test log
WebSocket traffic
Crash log
urlsession-crash.txt |
I ran the test suite against the in-progress However, while running the tests, I saw "unexpected" messages being received when the WebSocket was not in the connecting or open states for the same tests that typically cause this crash when using
|
@atdrendel that's great and it makes sense to me that we might receive a message during |
Unsolved thread on Developer Forums
The text was updated successfully, but these errors were encountered: