kie-ci3 commented on PR #3611:
URL: 
https://github.com/apache/incubator-kie-kogito-runtimes/pull/3611#issuecomment-2284131919

   
   **PR job** `#2` was: **UNSTABLE**
   Possible explanation: This should be test failures
   
   
   <details>
   <summary><b>Reproducer</b></summary>
   
   
   
   build-chain build full_downstream  -f 
'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml'
 -o 'bc' -p apache/incubator-kie-kogito-runtimes -u 
https://github.com/apache/incubator-kie-kogito-runtimes/pull/3611 
--skipParallelCheckout
   
   NOTE: To install the build-chain tool, please refer to 
https://github.com/kiegroup/github-action-build-chain#local-execution
   
   </details>
   
   
   Please look here: 
https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3611/2/display/redirect
   
   **Test results:**
   - PASSED: 3291
   - FAILED: 1
   
   Those are the test failures: 
   <details>
   <summary><a 
href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3611/2/testReport/org.kie.kogito.process.dynamic/DynamicCallResourceTest/___/";>org.kie.kogito.process.dynamic.DynamicCallResourceTest.(?)</a></summary>
   Unable to locate the artifact metadata file created that must be created by 
Quarkus in order to run integration tests. Make sure this test is run after 
'mvn package'. The easiest way to ensure this is by having the 
'maven-failsafe-plugin' run the test instead of the 'maven-surefire-plugin'.
   </details>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to