-
Notifications
You must be signed in to change notification settings - Fork 1.1k
hello world test periodically fails on first try #687
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
Labels
Milestone
Comments
@tejksat maybe you have any ideas for this case? |
@KostyaSha not yet.. I will take a look. |
@tejksat will be perfect as it heisenbug ! |
tejksat
added a commit
to tejksat/docker-java
that referenced
this issue
Aug 30, 2016
tejksat
added a commit
to tejksat/docker-java
that referenced
this issue
Aug 30, 2016
KostyaSha
added a commit
that referenced
this issue
Aug 30, 2016
possible fix merged, will be clear later whether it fixed it. |
tejksat
pushed a commit
to tejksat/docker-java
that referenced
this issue
Aug 31, 2016
Socket.shutdownOutput() javadoc states that "For a TCP socket, any previously written data will be sent followed by TCP's normal connection termination sequence.". When this happens Socket input (and so process stdout and stderr streams) becomes unavailable.
tejksat
pushed a commit
to tejksat/docker-java
that referenced
this issue
Aug 31, 2016
Socket.shutdownOutput() javadoc states that "For a TCP socket, any previously written data will be sent followed by TCP's normal connection termination sequence.". When this happens Socket input (and so process stdout and stderr streams) becomes unavailable.
issue could be reopened if issue appeared again. |
panuse
pushed a commit
to TuKangTech/docker-java
that referenced
this issue
Aug 20, 2017
panuse
pushed a commit
to TuKangTech/docker-java
that referenced
this issue
Aug 20, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I thought it was timeout initialisation issue but seems it didn't fix it.
The text was updated successfully, but these errors were encountered: