Skip to content

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

Closed
KostyaSha opened this issue Aug 29, 2016 · 5 comments
Closed

hello world test periodically fails on first try #687

KostyaSha opened this issue Aug 29, 2016 · 5 comments

Comments

@KostyaSha
Copy link
Member

Tests run: 323, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 561.622 sec <<< FAILURE! - in TestSuite
(com.github.dockerjava.netty.exec.AttachContainerCmdExecTest)  Time elapsed: 10.809 sec  <<< FAILURE!
java.lang.AssertionError: 
Expected: a string containing "hello world"
     but: was ""
    at com.github.dockerjava.netty.exec.AttachContainerCmdExecTest.attachContainerWithStdin(AttachContainerCmdExecTest.java:121)
Results :
Failed tests: 
com.github.dockerjava.netty.exec.AttachContainerCmdExecTest.(com.github.dockerjava.netty.exec.AttachContainerCmdExecTest)
  Run 1: AttachContainerCmdExecTest.attachContainerWithStdin:121 
Expected: a string containing "hello world"
     but: was ""
  Run 2: PASS
  Run 3: PASS

I thought it was timeout initialisation issue but seems it didn't fix it.

@KostyaSha
Copy link
Member Author

@tejksat maybe you have any ideas for this case?

@tejksat
Copy link
Contributor

tejksat commented Aug 30, 2016

@KostyaSha not yet.. I will take a look.

@KostyaSha
Copy link
Member Author

@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
Copy link
Member Author

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.
@KostyaSha
Copy link
Member Author

issue could be reopened if issue appeared again.

@KostyaSha KostyaSha added this to the 3.0.6 milestone Sep 13, 2016
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
Projects
None yet
Development

No branches or pull requests

2 participants