Skip to content
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

[KOGITO-7985] Job service integration tests improvements #1497

Merged
merged 14 commits into from
Nov 23, 2022

Conversation

tiagodolphine
Copy link
Contributor

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Pull Request title is properly formatted: KOGITO-XYZ Subject
  • Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
  • Pull Request contains link to the JIRA issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:
  • for pull request checks
    Please add comment: Jenkins retest this

  • for a specific pull request check
    Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] tests

  • for quarkus branch checks
    Run checks against Quarkus current used branch
    Please add comment: Jenkins run quarkus-branch

  • for a quarkus branch specific check
    Run checks against Quarkus current used branch
    Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-branch

  • for quarkus main checks
    Run checks against Quarkus main branch
    Please add comment: Jenkins run quarkus-main

  • for a specific quarkus main check
    Run checks against Quarkus main branch
    Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-main

  • for quarkus lts checks
    Run checks against Quarkus lts branch
    Please add comment: Jenkins run quarkus-lts

  • for a specific quarkus lts check
    Run checks against Quarkus lts branch
    Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-lts

  • for native checks
    Run native checks
    Please add comment: Jenkins run native

  • for a specific native check
    Run native checks
    Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] native

  • for mandrel checks
    Run native checks against Mandrel image
    Please add comment: Jenkins run mandrel

  • for a specific mandrel check
    Run native checks against Mandrel image
    Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] mandrel

  • for mandrel lts checks
    Run native checks against Mandrel image and quarkus lts branch
    Please add comment: Jenkins run mandrel-lts

  • for a specific mandrel lts check
    Run native checks against Mandrel image and quarkus lts branch
    Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] mandrel-lts

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 27, 2022

(tests) - kogito-apps job #487 was: FAILURE
Possible explanation: Pipeline failure or project build failure

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/487/display/redirect

Test results:

  • PASSED: 1899
  • FAILED: 8

Those are the test failures:

org.kie.kogito.it.jobs.ProcessAsyncIT.testAsync org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

org.kie.kogito.it.jobs.ProcessTimerIT.testTimers org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.util.concurrent.TimeoutException
org.kie.kogito.it.jobs.ProcessTimerIT.testCancelTimer org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

org.kie.kogito.taskassigning.service.SolverExecutorTest.stopWithSolverStarted java.util.concurrent.TimeoutException: stopWithSolverStarted() timed out after 80 seconds
at org.junit.jupiter.engine.extension.TimeoutExceptionFactory.create(TimeoutExceptionFactory.java:29)
at org.junit.jupiter.engine.extension.SameThreadTimeoutInvocation.proceed(SameThreadTimeoutInvocation.java:58)
at org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
at org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
at org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
at org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
at org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
at org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
at org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
at org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
at org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:41)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:155)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:41)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:155)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:35)
at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor.execute(HierarchicalTestExecutor.java:57)
at org.junit.platform.engine.support.hierarchical.HierarchicalTestEngine.execute(HierarchicalTestEngine.java:54)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:147)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:127)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:90)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:55)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:102)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:54)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:114)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:86)
at org.junit.platform.launcher.core.DefaultLauncherSession$DelegatingLauncher.execute(DefaultLauncherSession.java:86)
at org.junit.platform.launcher.core.SessionPerRequestLauncher.execute(SessionPerRequestLauncher.java:53)
at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.execute(JUnitPlatformProvider.java:188)
at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invokeAllTests(JUnitPlatformProvider.java:154)
at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:128)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Suppressed: java.lang.InterruptedException
at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:385)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
at org.kie.kogito.taskassigning.service.SolverExecutorTest.stopWithSolverStarted(SolverExecutorTest.java:133)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
at org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
at org.junit.jupiter.engine.extension.SameThreadTimeoutInvocation.proceed(SameThreadTimeoutInvocation.java:45)
... 64 more

See console log:

Console Logs [2022-10-27T21:39:43.499Z] [INFO] | +- io.quarkus:quarkus-vertx-http-deployment-spi:jar:2.13.3.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie.kogito:kogito-codegen-core:jar:2.0.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | | \- org.drools:drools-io:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie.kogito:kogito-codegen-api:jar:2.0.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | | \- com.github.javaparser:javaparser-core:jar:3.24.2:compile
[2022-10-27T21:39:43.499Z] [INFO] | \- org.kie:efesto-dependencies:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie:efesto-common-utils:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie:efesto-common-api:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie:efesto-common-core:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie:efesto-compilation-manager-api:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie:efesto-compilation-manager-core:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie:efesto-runtime-manager-api:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.kie:efesto-runtime-manager-core:jar:8.30.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | \- org.assertj:assertj-core:jar:3.22.0:test
[2022-10-27T21:39:43.499Z] [INFO] +- io.quarkus:quarkus-undertow-deployment:jar:2.13.3.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- io.quarkus.http:quarkus-http-servlet:jar:4.1.9:compile
[2022-10-27T21:39:43.499Z] [INFO] | | \- io.quarkus.http:quarkus-http-core:jar:4.1.9:compile
[2022-10-27T21:39:43.499Z] [INFO] | | +- io.quarkus.http:quarkus-http-http-core:jar:4.1.9:compile
[2022-10-27T21:39:43.499Z] [INFO] | | \- io.netty:netty-codec-http:jar:4.1.82.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | | \- io.netty:netty-codec:jar:4.1.82.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- jakarta.servlet:jakarta.servlet-api:jar:4.0.3:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- io.quarkus:quarkus-undertow-spi:jar:2.13.3.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- io.quarkus:quarkus-undertow:jar:2.13.3.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | | \- io.quarkus.http:quarkus-http-vertx-backend:jar:4.1.9:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- io.quarkus:quarkus-kubernetes-spi:jar:2.13.3.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | \- org.jboss.metadata:jboss-metadata-web:jar:15.1.0.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] | \- org.jboss.metadata:jboss-metadata-common:jar:15.1.0.Final:compile
[2022-10-27T21:39:43.499Z] [INFO] +- io.rest-assured:rest-assured:jar:4.5.1:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.codehaus.groovy:groovy:jar:3.0.9:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.codehaus.groovy:groovy-xml:jar:3.0.9:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.apache.httpcomponents:httpclient:jar:4.5.13:compile
[2022-10-27T21:39:43.499Z] [INFO] | | +- org.apache.httpcomponents:httpcore:jar:4.4.15:compile
[2022-10-27T21:39:43.499Z] [INFO] | | \- commons-codec:commons-codec:jar:1.15:compile
[2022-10-27T21:39:43.499Z] [INFO] | +- org.apache.httpcomponents:httpmime:jar:4.5.13:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.hamcrest:hamcrest:jar:2.1:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.ccil.cowan.tagsoup:tagsoup:jar:1.2.1:test
[2022-10-27T21:39:43.499Z] [INFO] | +- io.rest-assured:json-path:jar:4.5.1:test
[2022-10-27T21:39:43.499Z] [INFO] | | +- org.codehaus.groovy:groovy-json:jar:3.0.9:test
[2022-10-27T21:39:43.499Z] [INFO] | | \- io.rest-assured:rest-assured-common:jar:4.5.1:test
[2022-10-27T21:39:43.499Z] [INFO] | \- io.rest-assured:xml-path:jar:4.5.1:test
[2022-10-27T21:39:43.499Z] [INFO] +- org.mockito:mockito-core:jar:4.8.0:test
[2022-10-27T21:39:43.499Z] [INFO] | +- net.bytebuddy:byte-buddy:jar:1.12.9:test
[2022-10-27T21:39:43.499Z] [INFO] | +- net.bytebuddy:byte-buddy-agent:jar:1.12.14:test
[2022-10-27T21:39:43.499Z] [INFO] | \- org.objenesis:objenesis:jar:3.2:test
[2022-10-27T21:39:43.499Z] [INFO] +- org.kie.kogito:kogito-quarkus-serverless-workflow-devui:jar:2.0.0-SNAPSHOT:compile
[2022-10-27T21:39:43.499Z] [INFO] | \- jakarta.annotation:jakarta.annotation-api:jar:1.3.5:compile
[2022-10-27T21:39:43.499Z] [INFO] +- io.quarkus:quarkus-junit5-internal:jar:2.13.3.Final:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.jboss.shrinkwrap:shrinkwrap-depchain:pom:1.2.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | +- org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | +- org.jboss.shrinkwrap:shrinkwrap-spi:jar:1.2.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | \- org.jboss.shrinkwrap:shrinkwrap-impl-base:jar:1.2.6:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.junit.jupiter:junit-jupiter-api:jar:5.9.1:test
[2022-10-27T21:39:43.499Z] [INFO] | | +- org.opentest4j:opentest4j:jar:1.2.0:test
[2022-10-27T21:39:43.499Z] [INFO] | | \- org.junit.platform:junit-platform-commons:jar:1.9.1:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.junit.jupiter:junit-jupiter-params:jar:5.9.1:test
[2022-10-27T21:39:43.499Z] [INFO] | +- org.junit.jupiter:junit-jupiter-engine:jar:5.9.1:test
[2022-10-27T21:39:43.499Z] [INFO] | +- io.quarkus:quarkus-test-common:jar:2.13.3.Final:test
[2022-10-27T21:39:43.499Z] [INFO] | | +- io.quarkus:quarkus-bootstrap-maven-resolver:jar:2.13.3.Final:test
[2022-10-27T21:39:43.499Z] [INFO] | | | +- org.apache.maven:maven-embedder:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven:maven-settings:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven:maven-core:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | | +- org.apache.maven:maven-artifact:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | | \- org.codehaus.plexus:plexus-component-annotations:jar:1.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven:maven-plugin-api:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven:maven-model:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven:maven-model-builder:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven:maven-builder-support:jar:3.8.6:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven.resolver:maven-resolver-api:jar:1.6.3:test
[2022-10-27T21:39:43.499Z] [INFO] | | | | +- org.apache.maven.resolver:maven-resolver-util:jar:1.6.3:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.apache.maven.shared:maven-shared-utils:jar:3.3.4:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- com.google.inject:guice:jar:no_aop:4.2.2:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | | \- com.google.guava:guava:jar:31.1-jre:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | | \- com.google.guava:failureaccess:jar:1.0.1:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.codehaus.plexus:plexus-classworlds:jar:2.6.0:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.codehaus.plexus:plexus-sec-dispatcher:jar:2.0:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.codehaus.plexus:plexus-cipher:jar:2.0:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | \- commons-cli:commons-cli:jar:1.4:test
[2022-10-27T21:39:43.500Z] [INFO] | | | +- org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.3.5:test
[2022-10-27T21:39:43.500Z] [INFO] | | | +- org.apache.maven:maven-settings-builder:jar:3.8.6:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | \- org.codehaus.plexus:plexus-interpolation:jar:1.26:test
[2022-10-27T21:39:43.500Z] [INFO] | | | +- org.apache.maven:maven-resolver-provider:jar:3.8.6:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.apache.maven:maven-repository-metadata:jar:3.8.6:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.apache.maven.resolver:maven-resolver-spi:jar:1.6.3:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.apache.maven.resolver:maven-resolver-impl:jar:1.6.3:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | \- org.codehaus.plexus:plexus-utils:jar:3.3.0:test
[2022-10-27T21:39:43.500Z] [INFO] | | | +- org.apache.maven.resolver:maven-resolver-connector-basic:jar:1.6.3:test
[2022-10-27T21:39:43.500Z] [INFO] | | | +- org.apache.maven.resolver:maven-resolver-transport-wagon:jar:1.6.3:test
[2022-10-27T21:39:43.500Z] [INFO] | | | +- org.apache.maven.wagon:wagon-http:jar:3.5.1:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | +- org.apache.maven.wagon:wagon-http-shared:jar:3.5.1:test
[2022-10-27T21:39:43.500Z] [INFO] | | | | \- org.apache.maven.wagon:wagon-provider-api:jar:3.5.1:test
[2022-10-27T21:39:43.500Z] [INFO] | | | \- org.apache.maven.wagon:wagon-file:jar:3.5.1:test
[2022-10-27T21:39:43.500Z] [INFO] | | \- io.quarkus:quarkus-bootstrap-gradle-resolver:jar:2.13.3.Final:test
[2022-10-27T21:39:43.500Z] [INFO] | +- jakarta.enterprise:jakarta.enterprise.cdi-api:jar:2.0.2:compile
[2022-10-27T21:39:43.500Z] [INFO] | | \- jakarta.el:jakarta.el-api:jar:3.0.3:compile
[2022-10-27T21:39:43.500Z] [INFO] | \- org.awaitility:awaitility:jar:4.2.0:test
[2022-10-27T21:39:43.500Z] [INFO] \- org.kie.kogito:kogito-apps-ui-packages:pom:2.0.0-SNAPSHOT:compile
[2022-10-27T21:39:43.500Z] [INFO] ------------------------------------------------------------------------
[2022-10-27T21:39:43.500Z] [INFO] Reactor Summary for Kogito Apps 2.0.0-SNAPSHOT:
[2022-10-27T21:39:43.500Z] [INFO]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps ........................................ SUCCESS [ 3.812 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: BOM ................................. SUCCESS [ 0.051 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Build Parent BOM .................... SUCCESS [ 0.044 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons ................. SUCCESS [ 0.048 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons API ............. SUCCESS [ 2.571 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons Protobuf ........ SUCCESS [ 5.432 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons PostgreSQL ...... SUCCESS [ 19.923 s]
[2022-10-27T21:39:43.500Z] [INFO] Quarkus :: PostgreSQL :: In-memory :: Parent ....... SUCCESS [ 0.038 s]
[2022-10-27T21:39:43.500Z] [INFO] Quarkus :: PostgreSQL :: In-memory :: Runtime ...... SUCCESS [ 2.180 s]
[2022-10-27T21:39:43.500Z] [INFO] Quarkus :: PostgreSQL :: In-memory :: Deployment ... SUCCESS [ 20.827 s]
[2022-10-27T21:39:43.500Z] [INFO] Quarkus :: PostgreSQL :: In-memory :: Integration Tests SUCCESS [ 33.680 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons Infinispan ...... SUCCESS [ 41.892 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons MongoDB ......... SUCCESS [ 24.186 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons Redis ........... SUCCESS [ 5.681 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons Oracle .......... SUCCESS [ 54.083 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons :: Reporting :: Parent SUCCESS [ 0.045 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons :: Reporting :: API SUCCESS [ 5.710 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons :: Reporting :: PostgreSQL base SUCCESS [ 5.790 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Persistence Commons :: Reporting :: PostgreSQL (Generic) SUCCESS [ 26.192 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: DB Scripts Collection Multi Repo .... SUCCESS [ 0.278 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Jobs Service ........................ SUCCESS [ 0.024 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Jobs Service :: Common .............. SUCCESS [02:16 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Jobs Service :: Infinispan .......... SUCCESS [02:15 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Jobs Service :: PostgreSQL .......... SUCCESS [01:50 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Jobs Service :: MongoDB ............. SUCCESS [01:47 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Jobs Service :: In-memory ........... SUCCESS [01:46 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index .......................... SUCCESS [ 0.026 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage .................. SUCCESS [ 0.029 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage API .............. SUCCESS [ 1.368 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage Protobuf ......... SUCCESS [ 2.859 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage PostgreSQL ....... SUCCESS [ 23.701 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage Infinispan ....... SUCCESS [ 5.936 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage MongoDB .......... SUCCESS [ 18.403 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage PostgreSQL :: Reporting SUCCESS [ 23.834 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Storage Oracle DB ........ SUCCESS [ 50.218 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Service .................. SUCCESS [ 0.031 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Service Common ........... SUCCESS [ 17.872 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Service with In-memory persistence SUCCESS [01:53 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Service with Infinispan .. SUCCESS [02:51 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Service with MongoDB ..... SUCCESS [02:23 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Service with Oracle ...... SUCCESS [03:39 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Data Index Service with PostgreSQL .. SUCCESS [02:16 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: UI Packages ......................... SUCCESS [15:43 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Security Commons .................... SUCCESS [01:04 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Management Console .................. SUCCESS [ 15.598 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty UI ........................... SUCCESS [01:30 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Console ........................ SUCCESS [ 22.017 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Explainability ...................... SUCCESS [ 0.022 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Explainability Api .................. SUCCESS [ 3.422 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Explainability Service .............. SUCCESS [ 13.054 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty .............................. SUCCESS [ 0.029 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Storage ...................... SUCCESS [ 0.023 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Storage API .................. SUCCESS [ 3.653 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Service ...................... SUCCESS [ 0.021 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Service :: API ............... SUCCESS [ 0.278 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Explainability Service Messaging .... SUCCESS [ 35.729 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Explainability Service Rest ......... SUCCESS [ 51.859 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Storage Common ............... SUCCESS [ 0.183 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Storage Infinispan ........... SUCCESS [ 5.233 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Storage Redis ................ SUCCESS [ 3.934 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Storage PostgreSQL ........... SUCCESS [ 4.837 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Service Common ............... SUCCESS [02:07 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Service Infinispan ........... SUCCESS [ 35.570 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Service Redis ................ SUCCESS [ 27.386 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Trusty Service PostgreSQL ........... SUCCESS [ 33.779 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Assigning ...................... SUCCESS [ 0.021 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Assigning Core ................. SUCCESS [ 20.526 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Assigning Process Service Client SUCCESS [ 23.048 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Assigning :: Integration API ... SUCCESS [ 0.210 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Assigning :: User Service ...... SUCCESS [ 0.025 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Assigning :: User Service Properties SUCCESS [ 3.958 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Task Assigning Service .............. SUCCESS [01:40 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: JIT Executor ........................ SUCCESS [ 0.021 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: JIT Executor DMN .................... SUCCESS [ 32.774 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: JIT Executor Runner ................. SUCCESS [ 20.367 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests ................... SUCCESS [ 0.022 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service ... SUCCESS [ 0.023 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service :: Common SUCCESS [ 0.455 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Data Index ..... SUCCESS [ 0.027 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Data Index :: Common SUCCESS [ 0.475 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service :: Common :: Quarkus FAILURE [ 0.073 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service :: Quarkus SKIPPED
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service :: Quarkus :: Management SKIPPED
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service :: Quarkus :: Messaging SKIPPED
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service :: Quarkus :: Knative Eventing SKIPPED
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Jobs Service :: Spring Boot SUCCESS [35:35 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Trusty Service . SUCCESS [ 0.033 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Trusty Service :: Common SUCCESS [ 0.349 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Trusty Service :: Quarkus SUCCESS [01:06 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Trusty Audit UI SUCCESS [01:09 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Trusty Service :: Spring Boot SUCCESS [01:13 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Data Index :: Quarkus SUCCESS [02:20 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Data Index :: Spring Boot SUCCESS [01:50 min]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Task Assigning Service SUCCESS [ 0.028 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Task Assigning Service :: Processes SUCCESS [ 17.040 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Integration Tests :: Task Assigning Service :: Quarkus SUCCESS [ 37.947 s]
[2022-10-27T21:39:43.500Z] [INFO] Runtime Tools Quarkus Extension - Parent ........... SUCCESS [ 0.021 s]
[2022-10-27T21:39:43.500Z] [INFO] Runtime Tools Quarkus Extension - Runtime .......... SUCCESS [ 6.495 s]
[2022-10-27T21:39:43.500Z] [INFO] Runtime Tools Quarkus Extension - Deployment ....... SUCCESS [ 6.979 s]
[2022-10-27T21:39:43.500Z] [INFO] Kogito Apps :: Serverless Workflow Quarkus Dev UI Extension SUCCESS [ 0.023 s]
[2022-10-27T21:39:43.501Z] [INFO] Kogito Apps :: Serverless Workflow Quarkus Dev UI Extension :: Extension SUCCESS [ 5.875 s]
[2022-10-27T21:39:43.501Z] [INFO] Kogito Apps :: Serverless Workflow Quarkus Dev UI Extension :: Deployment SUCCESS [ 5.925 s]
[2022-10-27T21:39:43.501Z] [INFO] ------------------------------------------------------------------------
[2022-10-27T21:39:43.501Z] [INFO] BUILD FAILURE
[2022-10-27T21:39:43.501Z] [INFO] ------------------------------------------------------------------------
[2022-10-27T21:39:43.501Z] [INFO] Total time: 01:42 h
[2022-10-27T21:39:43.501Z] [INFO] Finished at: 2022-10-27T17:39:42-04:00
[2022-10-27T21:39:43.501Z] [INFO] ------------------------------------------------------------------------
[2022-10-27T21:39:43.501Z] [ERROR] Failed to execute goal net.revelc.code:impsort-maven-plugin:1.5.0:check (default) on project integration-tests-jobs-service-common-quarkus: Imports are not sorted in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-apps.tests.kogito-apps/bc/kiegroup_kogito_apps/kogito-apps/apps-integration-tests/integration-tests-jobs-service/integration-tests-jobs-service-common-quarkus/src/main/java/org/kie/kogito/test/resources/JobServiceComposeQuarkusTestResource.java -> [Help 1]
[2022-10-27T21:39:43.501Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal net.revelc.code:impsort-maven-plugin:1.5.0:check (default) on project integration-tests-jobs-service-common-quarkus: Imports are not sorted in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-apps.tests.kogito-apps/bc/kiegroup_kogito_apps/kogito-apps/apps-integration-tests/integration-tests-jobs-service/integration-tests-jobs-service-common-quarkus/src/main/java/org/kie/kogito/test/resources/JobServiceComposeQuarkusTestResource.java
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:375)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
[2022-10-27T21:39:43.501Z] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
[2022-10-27T21:39:43.501Z] at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
[2022-10-27T21:39:43.501Z] at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
[2022-10-27T21:39:43.501Z] at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
[2022-10-27T21:39:43.501Z] at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
[2022-10-27T21:39:43.501Z] at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
[2022-10-27T21:39:43.501Z] at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
[2022-10-27T21:39:43.501Z] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
[2022-10-27T21:39:43.501Z] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
[2022-10-27T21:39:43.501Z] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
[2022-10-27T21:39:43.501Z] at java.lang.reflect.Method.invoke (Method.java:566)
[2022-10-27T21:39:43.501Z] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
[2022-10-27T21:39:43.501Z] at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
[2022-10-27T21:39:43.501Z] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
[2022-10-27T21:39:43.501Z] at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[2022-10-27T21:39:43.501Z] Caused by: org.apache.maven.plugin.MojoFailureException: Imports are not sorted in /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-apps.tests.kogito-apps/bc/kiegroup_kogito_apps/kogito-apps/apps-integration-tests/integration-tests-jobs-service/integration-tests-jobs-service-common-quarkus/src/main/java/org/kie/kogito/test/resources/JobServiceComposeQuarkusTestResource.java
[2022-10-27T21:39:43.501Z] at net.revelc.code.impsort.maven.plugin.AbstractImpSortMojo.fail (AbstractImpSortMojo.java:308)
[2022-10-27T21:39:43.501Z] at net.revelc.code.impsort.maven.plugin.AbstractImpSortMojo.fail (AbstractImpSortMojo.java:304)
[2022-10-27T21:39:43.501Z] at net.revelc.code.impsort.maven.plugin.CheckMojo.processResult (CheckMojo.java:33)
[2022-10-27T21:39:43.501Z] at net.revelc.code.impsort.maven.plugin.AbstractImpSortMojo.lambda$execute$3 (AbstractImpSortMojo.java:249)
[2022-10-27T21:39:43.501Z] at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)
[2022-10-27T21:39:43.501Z] at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)
[2022-10-27T21:39:43.501Z] at java.util.stream.ForEachOps$ForEachOp$OfRef.accept (ForEachOps.java:183)
[2022-10-27T21:39:43.501Z] at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)
[2022-10-27T21:39:43.501Z] at java.util.Spliterators$ArraySpliterator.forEachRemaining (Spliterators.java:948)
[2022-10-27T21:39:43.501Z] at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)
[2022-10-27T21:39:43.501Z] at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)
[2022-10-27T21:39:43.501Z] at java.util.stream.ForEachOps$ForEachOp.evaluateSequential (ForEachOps.java:150)
[2022-10-27T21:39:43.501Z] at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential (ForEachOps.java:173)
[2022-10-27T21:39:43.501Z] at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
[2022-10-27T21:39:43.501Z] at java.util.stream.ReferencePipeline.forEach (ReferencePipeline.java:497)
[2022-10-27T21:39:43.501Z] at java.util.stream.ReferencePipeline$7$1.accept (ReferencePipeline.java:274)
[2022-10-27T21:39:43.501Z] at java.util.Spliterators$ArraySpliterator.forEachRemaining (Spliterators.java:948)
[2022-10-27T21:39:43.501Z] at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)
[2022-10-27T21:39:43.501Z] at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)
[2022-10-27T21:39:43.501Z] at java.util.stream.ReduceOps$ReduceTask.doLeaf (ReduceOps.java:952)
[2022-10-27T21:39:43.501Z] at java.util.stream.ReduceOps$ReduceTask.doLeaf (ReduceOps.java:926)
[2022-10-27T21:39:43.501Z] at java.util.stream.AbstractTask.compute (AbstractTask.java:327)
[2022-10-27T21:39:43.501Z] at java.util.concurrent.CountedCompleter.exec (CountedCompleter.java:746)
[2022-10-27T21:39:43.501Z] at java.util.concurrent.ForkJoinTask.doExec (ForkJoinTask.java:290)
[2022-10-27T21:39:43.501Z] at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec (ForkJoinPool.java:1020)
[2022-10-27T21:39:43.501Z] at java.util.concurrent.ForkJoinPool.scan (ForkJoinPool.java:1656)
[2022-10-27T21:39:43.501Z] at java.util.concurrent.ForkJoinPool.runWorker (ForkJoinPool.java:1594)
[2022-10-27T21:39:43.501Z] at java.util.concurrent.ForkJoinWorkerThread.run (ForkJoinWorkerThread.java:183)
[2022-10-27T21:39:43.501Z] [ERROR]
[2022-10-27T21:39:43.501Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[2022-10-27T21:39:43.501Z] [ERROR]
[2022-10-27T21:39:43.501Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[2022-10-27T21:39:43.501Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[2022-10-27T21:39:43.501Z] [ERROR]
[2022-10-27T21:39:43.501Z] [ERROR] After correcting the problems, you can resume the build with the command
[2022-10-27T21:39:43.501Z] [ERROR] mvn -rf :integration-tests-jobs-service-common-quarkus
[2022-10-27T21:39:43.756Z] ::error title= [kiegroup/kogito-apps] [Execution ERROR]::mvn -f kogito-apps/pom.xml clean install -Dvalidate-formatting -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-apps.tests.kogito-apps@tmp/config2470873036918223847tmp -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -Prun-code-coverage dependency:tree -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B
[2022-10-27T21:39:43.756Z] [INFO] Archive artifact won't be executed
[2022-10-27T21:39:43.756Z] ::group::[Pull Request Flow] Execution Summary...
[2022-10-27T21:39:43.756Z] [INFO] ----------------------------------------------
[2022-10-27T21:39:43.756Z] [INFO] [kiegroup/drools]. Execution Result: ok. Time: 3m 7.4s (187426 ms)
[2022-10-27T21:39:43.756Z] [INFO] [kiegroup/kogito-runtimes]. Execution Result: ok. Time: 3m 4.3s (184357 ms)
[2022-10-27T21:39:43.756Z] [INFO] [kiegroup/kogito-apps]. Execution Result: error. Time: 1h 42m 24.2s (6144276 ms)
[2022-10-27T21:39:43.756Z] [INFO] ----------------------------------------------
[2022-10-27T21:39:43.756Z] ::endgroup::
[2022-10-27T21:39:44.011Z] [ERROR] [kiegroup/kogito-apps] error executing command: 'mvn -f kogito-apps/pom.xml clean install -Dvalidate-formatting -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-apps.tests.kogito-apps@tmp/config2470873036918223847tmp -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -Prun-code-coverage dependency:tree -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B'. Message: Error: The process '/opt/tools/apache-maven-3.8.6/bin/mvn' failed with exit code 1
[2022-10-27T21:39:44.011Z] [ERROR] Command executions have failed, please review latest execution Error: [kiegroup/kogito-apps] error executing command: 'mvn -f kogito-apps/pom.xml clean install -Dvalidate-formatting -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-apps.tests.kogito-apps@tmp/config2470873036918223847tmp -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -Prun-code-coverage dependency:tree -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B'. Message: Error: The process '/opt/tools/apache-maven-3.8.6/bin/mvn' failed with exit code 1
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[2022-10-27T21:39:44.334Z] Deleting 1 temporary files
[Pipeline] // configFileProvider
[Pipeline] }
[Pipeline] // script
Post stage
[Pipeline] junit
[2022-10-27T21:39:44.433Z] Recording test results
[2022-10-27T21:39:55.975Z] [Checks API] No suitable checks publisher found.
[Pipeline] archiveArtifacts
[2022-10-27T21:39:55.996Z] Archiving artifacts
[Pipeline] script
[Pipeline] {
[Pipeline] sh
[2022-10-27T21:40:00.528Z] + rm -rf console.log
[Pipeline] sh
[2022-10-27T21:40:00.823Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/487/consoleText
[2022-10-27T21:40:00.823Z] + tail -n 300

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 28, 2022

(tests) - kogito-apps job #488 was: UNSTABLE
Possible explanation: This should be test failures

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/488/display/redirect

Test results:

  • PASSED: 1924
  • FAILED: 12

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.CallbackStateTimeoutsIT.callbackStateTimeoutsExceeded org.testcontainers.shaded.org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.test.TestUtils that uses java.lang.String, java.lang.Stringjava.lang.String 1 expectation failed.
Expected status code <404> but was <200>.
within 10 seconds.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <404> but was <200>.

Build projects / org.kie.kogito.it.jobs.ProcessAsyncIT.testAsync org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.BaseProcessAsyncIT 1 expectation failed.
JSON path hello doesn't match.
Expected: Hello Tiago
Actual: null
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
JSON path hello doesn't match.
Expected: Hello Tiago
Actual: null

Build projects / org.kie.kogito.it.jobs.ProcessAsyncIT.testAsync org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.BaseProcessTimerIT 1 expectation failed.
Expected status code <404> but was <200>.
within 10 seconds.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <404> but was <200>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimers org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.BaseProcessTimerIT 1 expectation failed.
Expected status code <404> but was <200>.
within 10 seconds.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <404> but was <200>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimers org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testCancelTimer org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.SwitchStateTimeoutsIT.switchStateEventConditionTimeoutsTransitionTimeoutsExceeded org.testcontainers.shaded.org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.test.TestUtils that uses java.lang.String, java.lang.Stringjava.lang.String 1 expectation failed.
Expected status code <404> but was <200>.
within 3 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <404> but was <200>.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 28, 2022

(tests) - kogito-apps job #489 was: UNSTABLE
Possible explanation: This should be test failures

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/489/display/redirect

Test results:

  • PASSED: 1929
  • FAILED: 7

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessAsyncIT.testAsync org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimers org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testCancelTimer org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Nov 7, 2022

(tests) - kogito-apps job #490 was: UNSTABLE
Possible explanation: This should be test failures

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/490/display/redirect

Test results:

  • PASSED: 1929
  • FAILED: 7

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessAsyncIT.testAsync org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimers org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testCancelTimer org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Nov 7, 2022

(tests) - kogito-apps job #491 was: UNSTABLE
Possible explanation: This should be test failures

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/491/display/redirect

Test results:

  • PASSED: 1929
  • FAILED: 7

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessAsyncIT.testAsync org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimers org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testCancelTimer org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.JobServiceHealthAware 1 expectation failed.
Expected status code <200> but was <503>.
within 5 minutes.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <200> but was <503>.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Nov 8, 2022

(tests) - kogito-apps job #492 was: FAILURE
Possible explanation: Pipeline failure or project build failure

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/492/display/redirect
See console log:

Console Logs [2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7440.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7441.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7442.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7443.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7444.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7445.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7446.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7447.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7449.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] du: cannot access ‘/home/jenkins/workspace/KIE/kogito/main/pullrequest/drools.tests.drools_ws-cleanup_1667911870309/bc/kiegroup_drools/drools/target/sonar/ucfg2/java/ucfg_7450.proto’: No such file or directory
[2022-11-08T12:51:15.313Z] 228M /home/jenkins/workspace/KIE/kogito/main
[2022-11-08T12:51:15.313Z] 228M /home/jenkins/workspace/KIE/kogito
[2022-11-08T12:51:15.313Z] 228M /home/jenkins/workspace/KIE
[2022-11-08T12:51:15.313Z] 228M /home/jenkins/workspace
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Install build-chain tool)
Stage "Install build-chain tool" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build projects)
Stage "Build projects" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Sonar analysis)
Stage "Sonar analysis" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (check space after build)
Stage "check space after build" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] script
[Pipeline] {
[Pipeline] sh
[2022-11-08T12:51:16.193Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/492/api/json
[Pipeline] readJSON
[Pipeline] sh

@tiagodolphine
Copy link
Contributor Author

jenkins retest this

@kie-ci3
Copy link
Contributor

kie-ci3 commented Nov 8, 2022

(tests) - kogito-apps job #494 was: UNSTABLE
Possible explanation: This should be test failures

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/494/display/redirect

Test results:

  • PASSED: 1931
  • FAILED: 5

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.BaseProcessTimerIT 1 expectation failed.
Expected status code <404> but was <200>.
within 10 seconds.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <404> but was <200>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.BaseProcessTimerIT 1 expectation failed.
Expected status code <404> but was <200>.
within 10 seconds.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <404> but was <200>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteTimerCycle java.lang.AssertionError:
1 expectation failed.
JSON path data.Jobs.size() doesn't match.
Expected: is <1>
Actual: <0>

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.BaseProcessTimerIT 1 expectation failed.
Expected status code <404> but was <200>.
within 10 seconds.
Caused by: java.util.concurrent.TimeoutException
Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testTimerCycle org.awaitility.core.ConditionTimeoutException:
Assertion condition defined as a lambda expression in org.kie.kogito.it.jobs.BaseProcessTimerIT 1 expectation failed.
Expected status code <404> but was <200>.
within 10 seconds.
Caused by: java.lang.AssertionError:
1 expectation failed.
Expected status code <404> but was <200>.

@tiagodolphine tiagodolphine marked this pull request as ready for review November 9, 2022 17:07
@tiagodolphine
Copy link
Contributor Author

@wmedvede @nmirasch I added some IT to test the end-to-end runtimes -> job service -> data-index, with persistence enabled, and for now the data-index integration is only on the kafka scenario, this is using test containers, with a kind of composable approach, I believe we need to improve it but, it is an initial step, it works we can create a shared module.

@wmedvede I also added an IT for the job-service leader election.

This is not the end result but a step forward in improving the ITs, let's see how it evolves.

assertJobsAndProcessOnDataIndex(TIMERS, id, "ABORTED", "CANCELED");
}

private void assertJobsAndProcessOnDataIndex(String processId, String processInstanceId, String processStatus, String jobStatus) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This assertion could be a good candidate to be refactored to the TestUtils class, there we have methods like assertProcessInstanceHasFinished, etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@@ -42,11 +43,16 @@ public abstract class BaseProcessTimerIT implements JobServiceHealthAware {
//Timers Tests
@Test
public void testTimers() {
String id = createTimer(new RequestPayload("PT02S"), TIMERS);
String id = createTimer(new RequestPayload("PT01S"), TIMERS);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

silly comment, but I believe "01" shouldn't be needed here, "PT1S" sounds more natural in my opinion.

}

//Boundary Timers Tests
@Test
public void testBoundaryTimersOnTask() {
String id = createTimer(new RequestPayload("PT02S"), TIMERS_ON_TASK);
String id = createTimer(new RequestPayload("PT01S"), TIMERS_ON_TASK);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here "01"

import org.testcontainers.containers.Network;
import org.testcontainers.containers.wait.strategy.Wait;

public class ComposeTestResource implements TestResource {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this class can be CompositeXXX instead of Compose

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1


@Override
public void start() {
LOGGER.info("Start JobService with {} test resources", sharedDependencyContainers.values().stream().map(GenericContainer::getImage).collect(Collectors.toList()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do this class always start a JobsService? if yes, the class should be JobsServiceCompositeXXXX, if not, we should fix this log line, maybe "Start CompositeService bla,bla, bla instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll change the logs, at first it was always starting a job service but in the end this could be a more generic composite class, and we can extract to a common module in the future

.map(c -> c.withNetwork(network))
.map(c -> c.waitingFor(Wait.forListeningPort()))
.forEach(GenericContainer::start);
//configurePostgreSQL(sharedDependencyContainers.values(), mainContainer);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if not used anymore, remove this line please.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1


@QuarkusIntegrationTest
@QuarkusTestResource(KogitoServiceRandomPortQuarkusTestResource.class)
@QuarkusTestResource(JobServiceQuarkusTestResource.class)
@QuarkusTestResource(KafkaQuarkusTestResource.class)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here


@QuarkusIntegrationTest
@QuarkusTestResource(KogitoServiceRandomPortQuarkusTestResource.class)
@QuarkusTestResource(JobServiceQuarkusTestResource.class)
@QuarkusTestResource(KafkaQuarkusTestResource.class)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here?

@QuarkusIntegrationTest
@QuarkusTestResource(KafkaQuarkusTestResource.class)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

</dependency>
<dependency>
<groupId>org.kie.kogito</groupId>
<artifactId>kogito-addons-quarkus-persistence-filesystem</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need this inclusion?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to generate the profo files in the data-index, but I'm not sure we need this, I used the same approach it was used in data-index ITs, c/c @nmirasch

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, didn't know that, thanks for the explanation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tiagodolphine @wmedvede I think it's not related with the proto files it's just another persistence type to test, but I never use this kind of persistence to define specific resources or test in the dataindex integration test. I'll try to double check this with @cristianonicolai.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, can we remove this? I'll give it a try, TBH I replicated what we have for the data-index ITs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can keep this. We use in data index for the reason you mentioned.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, yeah, we need to have one persistence enabled to have the proto files generated. Anyway, we can review this in the next PRs for ITs, for now, this works.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tiagodolphine, my fault! I was thinking in the different kind of persistence we are testing data-index. But it's true, the runtime uses this type to be able to generate the proto files..

@QuarkusIntegrationTest
@JobServiceTestResource(kafkaEnabled = true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A question that comes to min mind is, in general, AFAIK, when we have a group of test in Quarkus that uses a test resource like @JobServiceTestResource(kafkaEnabled = true), under the scene we have that the same resource instance is shared between the tests that uses it. (this is my understanding).
I our case, we have that for the same group of tests, we have that some uses
@JobServiceTestResource(kafkaEnabled = true) ( see that dataIndex is not enabled here)

however, some others to
@JobServiceTestResource(kafkaEnabled = true, dataIndexEnabled = true) (see that data index is enabled here)

however if the same resource is shared for the SwichStateTimeoutsIT and the ProcessTimerId, which instance wins?
the one with dataIndexEnabled = true or the one with dataIndexEnabled = false?

or maybe if the annotation configuration is different, two different instances of JobServiceTestResource are created?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

humm when running the tests the way it is, it seems the containers are created/stopped for each test class when looking at docker 🤔

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@@ -93,7 +93,7 @@ void startup(@Observes StartupEvent startupEvent) {
//background task for heartbeat will be started when become leader
heartbeat = vertx.periodicStream(TimeUnit.SECONDS.toMillis(heardBeatIntervalInSeconds))
.handler(t -> heartbeat(currentInfo.get())
.subscribe().with(i -> LOGGER.info("Heartbeat {}", currentInfo.get()),
.subscribe().with(i -> LOGGER.debug("Heartbeat {}", currentInfo.get()),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

.withDependencyToService(ComposeTestResource.MAIN_SERVICE_ID, postgreSqlContainer);
containers = resource.getServiceContainers(JobServiceContainer.class);
//decrease the leader expiration timeout to 2 seconds to make the test quicker
containers.stream().forEach(c -> c.withEnv("KOGITO_JOBS_SERVICE_MANAGEMENT_HEARTBEAT_EXPIRATION_IN_SECONDS", "2"));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can do containers.forEach directly here.

this.serviceContainers = new HashMap<>();
this.properties = new HashMap<>();
this.mainContainer = mainContainer;
withServiceContainer(MAIN_SERVICE_ID, mainContainer);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want to preserve the container adding and the subsequent startup order, maybe we need LinkedHashMap instead.
Please take a look a the JobServiceLeaderIT, I believe the testSingleLeader relies somethow on the start up order

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And regarding to keep the ordering in general, I think it could be a good thing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should not rely on the order IMO

.map(container -> healthRequest(container))
.collect(Collectors.toList());
//only one instance should be the leader (returning 200 OK)
assertThat(responses).containsExactlyInAnyOrder(200, 503, 503);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see my comments in CompositeResource, I think this test relies on the start-up order, but I'm not sure the startup order is warranted in the CompositeResource.

But independently of this, another question that comes to my mind is if it's safe to rely on the start-up order of the containers. From the theoretically point of view yes, but.., could it be possible (considering that containers starts one after another immediately) that container2 takes leadership, even when it was started a millisecond after container1.
Really only god knows.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test does not rely on the startup order, that's why it is being used containsExactlyInAnyOrder, the leader election does not require any order, the only thing it relies on is only one leader must be active no matter the order.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry Tiago, yeah, this is ok, my fault, I read the method name wrong 😞

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, no problem so we are aligned about that

List<Integer> responses = remain.stream()
.map(container -> healthRequest(container))
.collect(Collectors.toList());
assertThat(responses).containsExactlyInAnyOrder(200, 503);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, not sure if we can warranty the order...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

containsExactlyInAnyOrderso any order, we just need to guarantee there is one of them returning 200OK, that is the leader, no matter the order.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, I read it wrong.

Copy link
Contributor

@wmedvede wmedvede left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @tiagodolphine , good job! I left some comments, take a look please.
Thanks!

@tiagodolphine
Copy link
Contributor Author

@wmedvede I updated the PR based on your comments, can you take another round of review?
Thanks

Copy link
Contributor

@wmedvede wmedvede left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Tiago,
one last comment, not blocker, but if it can be done, I think it'll be great.

This three classes below, are integration tests, and have assertions, etc. but are located in the src/main directory. I believe we should move them to the src/test directory.

Note that sonar is also complaining about this.

Thanks!

integration-tests-jobs-service-common-quarkus/src/main/java/org/kie/kogito/it/jobs/BaseCallbackStateTimeoutsIT.java

integration-tests-jobs-service-common-quarkus/src/main/java/org/kie/kogito/it/jobs/BaseCallbackStateTimeoutsIT.java

integration-tests-jobs-service-common-quarkus/src/main/java/org/kie/kogito/it/jobs/BaseCallbackStateTimeoutsIT.java

@tiagodolphine
Copy link
Contributor Author

done

@tiagodolphine
Copy link
Contributor Author

@MarianMacik @nmirasch any comments from your side?

@nmirasch
Copy link
Contributor

@tiagodolphine code looks good, but when I give this a try It throws this error:

https://gist.github.com/nmirasch/0cccaf68250b7d648aa188d059d34d8e

@wmedvede could you double check?

@wmedvede
Copy link
Contributor

@tiagodolphine code looks good, but when I give this a try It throws this error:

https://gist.github.com/nmirasch/0cccaf68250b7d648aa188d059d34d8e

@wmedvede could you double check?

True thing, I've got same error locally. Let's see when the builds finish.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Nov 18, 2022

(tests) - kogito-apps job #500 was: UNSTABLE
Possible explanation: This should be test failures

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-apps.tests.kogito-apps/500/display/redirect

Test results:

  • PASSED: 1936
  • FAILED: 1

Those are the test failures:

org.kie.kogito.it.jobs.KafkaBaseSwitchStateTimeoutsIT.switchStateEventConditionTimeoutsTransitionTimeoutsExceeded java.util.NoSuchElementException: SRCFG00014: The config property kafka.bootstrap.servers is required but it could not be found in any config source
at org.kie.kogito.it.jobs.KafkaBaseSwitchStateTimeoutsIT.setup(KafkaBaseSwitchStateTimeoutsIT.java:36)

@mbiarnes
Copy link
Contributor

@tiagodolphine
Copy link
Contributor Author

@tiagodolphine code looks good, but when I give this a try It throws this error:

https://gist.github.com/nmirasch/0cccaf68250b7d648aa188d059d34d8e

@wmedvede could you double check?

humm ok let me take a look, thanks for reporting that @nmirasch @wmedvede

Copy link
Contributor

@nmirasch nmirasch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test look good, I didn't make it work at my local environment it could be my machine regarding this has the jenkins green. Thanks @tiagodolphine!


Persistence persistence() default Persistence.POSTGRESQL;

boolean knativeEventingEnabled() default false;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tiagodolphine @wmedvede we were thinking about similar issue on Data Index, but not sure we can/how to to od IT test for knative. Any ideas? @nmirasch FYI

@QuarkusIntegrationTest
@QuarkusTestResource(KafkaQuarkusTestResource.class)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tiagodolphine Haven't looked in deep, but if possible, we should start relying more on Quarkus Dev services instead.

</dependency>
<dependency>
<groupId>org.kie.kogito</groupId>
<artifactId>kogito-addons-quarkus-persistence-filesystem</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can keep this. We use in data index for the reason you mentioned.


kogito.persistence.type=filesystem

quarkus.devservices.enabled=false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is related to what I mentioned that we could rely on devservices instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cristianonicolai I tried to explain the issue in the other comment, but mixing dev services for these ITs won't bring benefit, basically, we need to customize the containers like sharing the same network, and setting env variables to allow all of them to work together.

runtimes -> kafka -> job-service -> kafka -> data-index 
 |                     |                              |
 |------------------ Integration test------------------      

@nmirasch ^

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tiagodolphine yeah, makes sense. In scenarios where we have multiple containers to start, we probably need to keep this setup as it is. Thanks for the details

@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 6 Code Smells

7.0% 7.0% Coverage
0.0% 0.0% Duplication

@tiagodolphine
Copy link
Contributor Author

Jenkins run native

@tiagodolphine tiagodolphine merged commit 7c7f510 into apache:main Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants