You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2025. It is now read-only.
On a few behave tests on containers that don't have a stable entrypoint (it runs and dies immediately), Cekit might hang trying to fetch the current process, hence failing the test execution or timing out.
We should start these containers via container is started with command bash, so it makes the container available to make the verifications needed.
Since it's making cekit hanging trying to ps a dead container. The container starts and dies since the truststore is invalid, cekit tries to ps to get the log and hangs.
ricardozanini
changed the title
Change the custom certificate behave test to avoid killing the container so Cekit can verify the logs
Change behave tests on containers that dies on startup
Dec 28, 2023
On a few behave tests on containers that don't have a stable entrypoint (it runs and dies immediately), Cekit might hang trying to fetch the current process, hence failing the test execution or timing out.
We should start these containers via
container is started with command bash
, so it makes the container available to make the verifications needed.See the
ignore
d list of tests in this PR: #1720Context
I've added an
ignore
tag to theVerify if a custom certificate is correctly handled
:https://github.com/apache/incubator-kie-kogito-images/blob/main/tests/features/common-custom-truststore.feature#L21
Since it's making cekit hanging trying to
ps
a dead container. The container starts and dies since the truststore is invalid, cekit tries to ps to get the log and hangs.Originally posted by @ricardozanini in #1720 (comment)
The text was updated successfully, but these errors were encountered: