-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Help needed: launch integration tests from master branch #859
Comments
I suspected problem whith parallelism. It is not.
|
@antechrestos could you share the commands you are using to execute the integration tests? Thanks |
Can you also share the git ref you are executing the tests again. I'm slightly confused because you mention master, but the log output looks like the failure is on a newly introduced test |
@cvgw i launch integration tests as specified in the documentation
Thank you |
@cvgw I join you the last test I made. In the log you can see that:
Also, before running the tests
Thanks! |
@antechrestos I'm fairly certain what you are seeing is a known race condition in docker. I sometimes see it on my own machine as well. Here is an issue that I believe is relevant docker/for-linux#711 Unfortunately I don't have any answers on how to fix it; I'm still working on resolving it on my own machine. |
@cvgw thank I will give it a try by tomorrow! |
@cvgw Adding |
@antechrestos I'm glad to hear that fixed it for you! Unfortunately that doesn't seem to fix it for my machine; perhaps it is dependent on the platform or something like that? |
Looks like this issue is resolved. |
@tejal29 Yeah sorry, I forgot to close it. Thanks |
Actual behavior
I created a gcs bucket and a repository to launch integration tests. I am running on ubuntu 18.04 and go 1.12.
I am trying to validate my development environment as my IT tests failed on my PR and I want to understand what happened.
Every time I launch it from
master
branch, I keep having random errors such asor
or else
Is there anything I am missing?
The text was updated successfully, but these errors were encountered: