-
Notifications
You must be signed in to change notification settings - Fork 23
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
Cekit hangs in container.execute(ps -C java,False) for simple behave tests #68
Comments
@jmtd Is this another issue with behave tests? |
@rnc I think the runner is in this repo, right? Not sure if it's related to the behave test, to me is more how we run it. Anyhow, I think you can move this issue there if that makes sense to you. |
@ricardozanini Ooops. Apologies, I was looking on my phone and missed the repository. |
@ricardozanini I think this hang is from the behave test invocations in this repository not cekit per se. |
Sorry for the delay in getting back to this.
To be clear, what times out here? The GHA action, or the individual test (i.e. behave is timing out that test), or the whole test run (but not killed by GHA)? I think what's happening is that my recently-merged changes to behave-test-steps (intended to resolve a very similar issue) have created a new problem. The intention of my changes was to wrap some of the docker API calls in a "monitor" which would time out if the call didn't return, failing a particular test, but not the whole test run. Clearly this isn't working quite right, so I think the next step should probably be to revert all my recent changes and go back to the drawing board. |
FWIW I can't reproduce the problem locally with the example test here and registry.access.redhat.com/ubi8/openjdk-17:1.19 |
@jmtd what is timing out is the individual tests. IIRC there's a hardcoded (default) timeout in 30s in the cekit code. Cekit tries to run the given command in the container and it fails after 30s, as exemplified in the logs. This is happening within a Jenkins node machine. But lately, I'm also seeing this same problem with MacOS running with colima. |
Describe the bug
I have a simple behave tests that execute fairly fast commands in my container to verify if the configuration is correct:
Then when running with
cekit behave command
I got the process hanging in:Until it times out.
To reproduce
Just run cekit build with behave in a image based on
registry.access.redhat.com/ubi8/openjdk-17:1.19
with the test described above.Expected behavior
That the test runs without timing out.
Logs
Environment information:
Additional context
You can see a PR with this image for reference here: apache/incubator-kie-kogito-images#1754
The text was updated successfully, but these errors were encountered: