-
Notifications
You must be signed in to change notification settings - Fork 173
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 Test: FullDuplexAndSequentialModeTest #1894
Comments
https://github.com/apple/servicetalk/pull/1910/checks?check_run_id=4174863283
|
https://github.com/apple/servicetalk/pull/2120/checks?check_run_id=5369476655
|
|
https://github.com/apple/servicetalk/pull/2278/checks?check_run_id=7530726644
|
https://github.com/apple/servicetalk/pull/2384/checks?check_run_id=8692706122
|
https://github.com/apple/servicetalk/pull/2412/checks?check_run_id=9259610509
|
https://github.com/apple/servicetalk/pull/2617/checks?check_run_id=14275302128
|
https://github.com/apple/servicetalk/pull/2632/checks?check_run_id=14668901643
|
https://github.com/apple/servicetalk/pull/2637/checks?check_run_id=14772117181
|
https://github.com/apple/servicetalk/runs/17378458627
|
https://github.com/apple/servicetalk/pull/2746/checks?check_run_id=18514248259
|
https://github.com/apple/servicetalk/pull/2787/checks?check_run_id=19649058298
|
The failures in The next question is how that could be happening given it has 30 seconds to get there which is a good amount of time even in CI. These tests are starting and stoping listeners and making connections, and the base class of this test alone is running on the order of 500 tests, meaning creating and destroying at roughly that many servers and clients. Maybe the tests are running into ephemeral port starvation issues which result in timeouts. |
https://github.com/apple/servicetalk/pull/2798/checks?check_run_id=20393836300
|
https://github.com/apple/servicetalk/actions/runs/8456122982/job/23165152255?pr=2776
|
https://github.com/apple/servicetalk/pull/1892/checks?check_run_id=3921774002
The text was updated successfully, but these errors were encountered: