Closed jstastny-cz closed 10 months ago
PR job #1
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1895/1/display/redirect
Test results:
Those are the test failures:
Jobs service test failures are known issues.
CallbackStateTimeoutsIT.callbackStateTimeoutsExceeded is not clear, maybe random fail?
Validated the logs by downloading the consoleText output from https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/view/change-requests/job/PR-1895/1/consoleText and executing following command with single value output:
[jstastny@IBM-PF3JSA31:/tmp]$ cat consoleText | sed -n 's#.*Container quay.io\/keycloak\/keycloak\(.*\)is starting.*#\1#p' | uniq
:20.0.2
Which means only the desired keycloak containers are started now.
PR job #2
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1895/2/display/redirect
Test results:
Those are the test failures:
I am going ahead with the merge to stop wasting build resources by running unused services.
apache/incubator-kie-issues#626
Disabling Keycloak dev service that is started by default when quarkus-oidc maven dependency is used (https://quarkus.io/guides/dev-services#keycloak).
Given that our tests instead of the Dev service rely on
org.kie.kogito.testcontainers.quarkus.KeycloakQuarkusTestResource
, the dev service started for no use and also caused failures due to strict startTimeout = 60s which was often exceeded. (even after apache/incubator-kie-issues#622 was fixed, because is a different thing)Also there was version mismatch between the Keycloak image versions being used - that was the main reason to dig into this topic in first place.