-
Notifications
You must be signed in to change notification settings - Fork 404
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
Sporadic failures due used tcp ports #5008
Comments
I've also seen this in
|
|
@andreipaduroiu -- Or somehow there's a race for the port it found? I was testing in a constrained environment, so if closing the tested port is async, maybe it isn't closed yet by the time the test tries to open the port that was found for it? Binding to port 0 and then looking up what port the OS assigned is probably a better strategy. |
Updates:
|
@shrids -- I was testing in a constrained environment, so I was running into every intermittent failure that results from coarse-grained timing issues (bind failure was just one of many observed failures, see #4998). My suggestion was more to do with moving away from opening and closing a throwaway socket, but that would require refactoring of our server components to expose I expect the timing failure I was seeing around bind has more to do with the open/close of the socket and less to do with how the port number was being determined. Maybe either case needs |
Seen in recent failed Actions build:
|
|
This change couldn't have possibly made any difference. The current code:
... sets the This leads me to believe the PR associated with this issue had no effect. Whatever the root cause is for this problem, it is still unaddressed. |
Another reproduction in the jenkins build.
|
Fixed via #4999. |
We still see problems binding ports, so reopening. |
Every location that is encountering this should be sure that it is setting |
Problem description
Sporadic failures with ControllerServiceStarter
Problem location
Free port detection logic
Suggestions for an improvement
Fix the issue.
The text was updated successfully, but these errors were encountered: