kie-ci3 commented on PR #3912: URL: https://github.com/apache/incubator-kie-kogito-runtimes/pull/3912#issuecomment-2916196459
**PR job** `#41` 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/3912 --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-3912/41/display/redirect **Test results:** - PASSED: 3596 - FAILED: 10 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-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesValuesMutable/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesValuesMutable</a></summary> <br/>Strict stubbing argument mismatch. Please check:<br/> - this invocation of 'prefixScan' method:<br/> store.prefixScan(<br/> "process-aProcessId",<br/> org.apache.kafka.common.serialization.StringSerializer@7227926b<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.stream(KafkaProcessInstances.java:194)<br/> - has following stubbing(s) with different arguments:<br/> 1. store.prefixScan(null, null);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesValuesMutable(KafkaProcessInstancesTest.java:184)<br/>Typically, stubbing argument mismatch indicates user mistake when writing tests.<br/>Mockito fails early so that you can debug potential problem easily.<br/>However, there are legit scenarios when this exception generates false negative signal:<br/> - stubbing the same method multiple times using 'given().will()' or 'when().then()' API<br/> Please use 'will().given()' or 'doReturn().when()' API for stubbing.<br/> - stubbed method is intentionally invoked with different arguments by code under test<br/> Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).<br/>For more information see javadoc for PotentialStubbingProblem class. </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesCreateDuplicate/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesCreateDuplicate</a></summary> <br/>Expecting actual throwable to be an instance of:<br/> org.kie.kogito.process.ProcessInstanceDuplicatedException<br/>but was:<br/> org.mockito.exceptions.misusing.PotentialStubbingProblem: <br/>Strict stubbing argument mismatch. Please check:<br/> - this invocation of 'get' method:<br/> store.get(<br/> "process-aProcessId-1423041a-a77d-42ad-b6ec-5a757ae4b40c"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.getProcessInstanceById(KafkaProcessInstances.java:115)<br/> - has following stubbing(s) with different arguments:<br/> 1. store.get(<br/> "aProcessId-1423041a-a77d-42ad-b6ec-5a757ae4b40c"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesCreateDuplicate(KafkaProcessInstancesTest.java:272)<br/>Typically, stubbing argument mismatch indicates user mistake when writing tests.<br/>Mockito fails early so that you can debug potential problem easily.<br/>However, there are legit scenarios w hen this exception generates false negative signal:<br/> - stubbing the same method multiple times using 'given().will()' or 'when().then()' API<br/> Please use 'will().given()' or 'doReturn().when()' API for stubbing.<br/> - stubbed method is intentionally invoked with different arguments by code under test<br/> Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).<br/>For more information see javadoc for PotentialStubbingProblem class.<br/> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.getProcessInstanceById(KafkaProcessInstances.java:115)<br/> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.create(KafkaProcessInstances.java:137)<br/> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.lambda$testProcessInstancesCreateDuplicate$4(KafkaProcessInstancesTest.java:276)<br/> ...(79 remaining lines not displayed - this can be changed with Assertions.setMaxStackTraceElementsDisplayed) </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesSize/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesSize</a></summary> <br/>Strict stubbing argument mismatch. Please check:<br/> - this invocation of 'prefixScan' method:<br/> store.prefixScan(<br/> "process-aProcessId",<br/> org.apache.kafka.common.serialization.StringSerializer@642c5bb3<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.stream(KafkaProcessInstances.java:194)<br/> - has following stubbing(s) with different arguments:<br/> 1. store.prefixScan(null, null);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesSize(KafkaProcessInstancesTest.java:190)<br/>Typically, stubbing argument mismatch indicates user mistake when writing tests.<br/>Mockito fails early so that you can debug potential problem easily.<br/>However, there are legit scenarios when this exception generates false negative signal:<br/> - stubbing the same method multiple times using 'given().will()' or 'when().then()' API<br/> Please use 'will().given()' or 'doReturn().when()' API for stubb ing.<br/> - stubbed method is intentionally invoked with different arguments by code under test<br/> Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).<br/>For more information see javadoc for PotentialStubbingProblem class. </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesCreate/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesCreate</a></summary> Unable to persist process instance id: c7222329-4ffa-4560-a060-2ffd7a2d1036 </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesExists/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesExists</a></summary> <br/>Strict stubbing argument mismatch. Please check:<br/> - this invocation of 'get' method:<br/> store.get(<br/> "process-aProcessId-e1c514cf-b4d4-4bba-ae4b-2eb1a5e78d8d"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.getProcessInstanceById(KafkaProcessInstances.java:115)<br/> - has following stubbing(s) with different arguments:<br/> 1. store.get(<br/> "aProcessId-e1c514cf-b4d4-4bba-ae4b-2eb1a5e78d8d"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesExists(KafkaProcessInstancesTest.java:123)<br/>Typically, stubbing argument mismatch indicates user mistake when writing tests.<br/>Mockito fails early so that you can debug potential problem easily.<br/>However, there are legit scenarios when this exception generates false negative signal:<br/> - stubbing the same method multiple times using 'given().will()' or 'when().then()' API<br/> Please use 'will().given()' or 'doReturn().when()' API for stubbing.<br/> - stubbed method is intentionally invoked with different arguments by code under test<br/> Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).<br/>For more information see javadoc for PotentialStubbingProblem class. </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesFindByIdReadOnly/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesFindByIdReadOnly</a></summary> <br/>Strict stubbing argument mismatch. Please check:<br/> - this invocation of 'get' method:<br/> store.get(<br/> "process-aProcessId-c356e9d9-374f-4853-8e8d-ea4cc11f63db"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.getProcessInstanceById(KafkaProcessInstances.java:115)<br/> - has following stubbing(s) with different arguments:<br/> 1. store.get(<br/> "aProcessId-c356e9d9-374f-4853-8e8d-ea4cc11f63db"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesFindByIdReadOnly(KafkaProcessInstancesTest.java:143)<br/>Typically, stubbing argument mismatch indicates user mistake when writing tests.<br/>Mockito fails early so that you can debug potential problem easily.<br/>However, there are legit scenarios when this exception generates false negative signal:<br/> - stubbing the same method multiple times using 'given().will()' or 'when().then()' API<br/> Please use 'will().given()' or 'doReturn ().when()' API for stubbing.<br/> - stubbed method is intentionally invoked with different arguments by code under test<br/> Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).<br/>For more information see javadoc for PotentialStubbingProblem class. </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesRemove/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesRemove</a></summary> Unable to remove process instance id: a957942e-5d8c-4678-8b11-a7f1adb5089b </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesUpdate/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesUpdate</a></summary> Unable to update process instance id: 6ff95bfa-eac0-452a-8e94-ad8ef961e722 </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesValues/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesValues</a></summary> <br/>Strict stubbing argument mismatch. Please check:<br/> - this invocation of 'prefixScan' method:<br/> store.prefixScan(<br/> "process-aProcessId",<br/> org.apache.kafka.common.serialization.StringSerializer@62dc1203<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.stream(KafkaProcessInstances.java:194)<br/> - has following stubbing(s) with different arguments:<br/> 1. store.prefixScan(null, null);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesValues(KafkaProcessInstancesTest.java:177)<br/>Typically, stubbing argument mismatch indicates user mistake when writing tests.<br/>Mockito fails early so that you can debug potential problem easily.<br/>However, there are legit scenarios when this exception generates false negative signal:<br/> - stubbing the same method multiple times using 'given().will()' or 'when().then()' API<br/> Please use 'will().given()' or 'doReturn().when()' API for stu bbing.<br/> - stubbed method is intentionally invoked with different arguments by code under test<br/> Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).<br/>For more information see javadoc for PotentialStubbingProblem class. </details> <details> <summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3912/41/testReport/org.kie.kogito.persistence.kafka/KafkaProcessInstancesTest/testProcessInstancesFindById/";>org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesFindById</a></summary> <br/>Strict stubbing argument mismatch. Please check:<br/> - this invocation of 'get' method:<br/> store.get(<br/> "process-aProcessId-e82af75e-c15c-4d71-af57-b8f621aef860"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstances.getProcessInstanceById(KafkaProcessInstances.java:115)<br/> - has following stubbing(s) with different arguments:<br/> 1. store.get(<br/> "aProcessId-e82af75e-c15c-4d71-af57-b8f621aef860"<br/>);<br/> -> at org.kie.kogito.persistence.kafka.KafkaProcessInstancesTest.testProcessInstancesFindById(KafkaProcessInstancesTest.java:133)<br/>Typically, stubbing argument mismatch indicates user mistake when writing tests.<br/>Mockito fails early so that you can debug potential problem easily.<br/>However, there are legit scenarios when this exception generates false negative signal:<br/> - stubbing the same method multiple times using 'given().will()' or 'when().then()' API<br/> Please use 'will().given()' or 'doReturn().when( )' API for stubbing.<br/> - stubbed method is intentionally invoked with different arguments by code under test<br/> Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).<br/>For more information see javadoc for PotentialStubbingProblem class. </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]
