-
Notifications
You must be signed in to change notification settings - Fork 79
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
Flaky tests and/or goroutine leaks #270
Comments
At least the test https://github.com/pion/sctp/actions/runs/5021866113/jobs/9004672764 |
The above log has expired. When I ran locally, I saw this error at high occurrance:
What failed was not TestAssociation_Shutdown but the cause was |
Now I see the ci test error:
|
Added createConnectedUDPConnPair(). Relates to #270
I have been trying different things and I finally got some clue why TestAssociation_Shutdown fails. Write operation on a net.Conn (a connected UDP using loopback interface) fails with some permission error: https://github.com/pion/sctp/actions/runs/7363064418/job/20042145678?pr=292
Does any one have any idea what could cause this logs message? |
This might be related: golang/go#63322 Also see quick-go's workaround:quic-go/quic-go@86de97c |
FYI: |
I have tried quick-go's workaround but now it causes a connection refuse error on the reader side which really does not make any sense. At this point, I am leaning toward not using the mutually connected UDPConn pair in the test, and use a mocked net.Conn, or vnet instead. pion/sctp does not actually use the mutually connected UDPConn anyway.
|
This is avoid the issue with unexpected errors occur on Ubuntu linux. Relates to #270
This is avoid the issue with unexpected errors occur on Ubuntu linux. Relates to #270
Now I am using a mock'd connection using "dumbConn2". Now, all the flaky tests are stable and ready for review. |
This is avoid the issue with unexpected errors occur on Ubuntu linux. Relates to #270
This is avoid the issue with unexpected errors occur on Ubuntu linux. Relates to #270
Your environment.
What did you do?
I run
go test -v -count=5 ./...
on themaster
-branch.What did you expect?
I expected all tests to pass all the time.
What happened?
I frequently see tests fail with either
Unexpected routines on test startup
orgoroutine is leaked
.The text was updated successfully, but these errors were encountered: