[incubator-kie-issues#1457] Allow grouping of events #3654
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fjtirado
force-pushed
the
incubator-kie-issues#1457
branch
2 times, most recently
from
767b563
to
e3735f1
Compare
|
PR job Reproducerbuild-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 #3654 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3654/2/display/redirect Test results:
Those are the test failures: org.kie.kogito.quarkus.workflows.CallbackStateIT.callbackStateWithErrorExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateIT.callbackStateSuccessfulExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateWithErrorExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateTimeoutsSuccessfulExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateWithTimeoutsErrorHandlerIT.callbackStateWithErrorExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateWithTimeoutsErrorHandlerIT.callbackStateTimeoutsSuccessfulExpecting value to be true but was false org.kie.kogito.quarkus.workflows.PojoServiceIT.testPojoExpecting value to be true but was false org.kie.kogito.quarkus.workflows.PojoServiceIT.testTypesPojoExpecting value to be true but was false org.kie.kogito.quarkus.workflows.PojoServiceIT.testFilterPojoExpecting value to be true but was false org.kie.kogito.quarkus.workflows.WorkflowEventIT.testWorkflowEventsjava.util.concurrent.TimeoutExceptionat java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960) at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095) at org.kie.kogito.quarkus.workflows.WorkflowEventIT.testWorkflowEvents(WorkflowEventIT.java:118) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) org.kie.kogito.quarkus.workflows.WorkflowEventIT.testWorkflowDefinitionsEventsAssertion condition defined as a org.kie.kogito.quarkus.workflows.WorkflowEventITExpected size: 57 but was: 0 in: [] within 10 seconds. org.kie.kogito.integrationtests.quarkus.ProcessEventIT.testSaveTaskjava.util.concurrent.TimeoutExceptionat java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960) at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095) at org.kie.kogito.integrationtests.quarkus.ProcessEventIT.testSaveTask(ProcessEventIT.java:200) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) |
|
PR job Reproducerbuild-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 #3654 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3654/3/display/redirect Test results:
Those are the test failures: org.kie.kogito.quarkus.workflows.CallbackStateIT.callbackStateWithErrorExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateIT.callbackStateSuccessfulExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateWithErrorExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateTimeoutsSuccessfulExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateWithTimeoutsErrorHandlerIT.callbackStateWithErrorExpecting value to be true but was false org.kie.kogito.quarkus.workflows.CallbackStateWithTimeoutsErrorHandlerIT.callbackStateTimeoutsSuccessfulExpecting value to be true but was false org.kie.kogito.quarkus.workflows.PojoServiceIT.testPojoExpecting value to be true but was false org.kie.kogito.quarkus.workflows.PojoServiceIT.testTypesPojoExpecting value to be true but was false org.kie.kogito.quarkus.workflows.PojoServiceIT.testFilterPojoExpecting value to be true but was false org.kie.kogito.quarkus.workflows.WorkflowEventIT.testWorkflowEventsjava.util.concurrent.TimeoutExceptionat java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960) at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095) at org.kie.kogito.quarkus.workflows.WorkflowEventIT.testWorkflowEvents(WorkflowEventIT.java:118) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) org.kie.kogito.quarkus.workflows.WorkflowEventIT.testWorkflowDefinitionsEventsAssertion condition defined as a org.kie.kogito.quarkus.workflows.WorkflowEventITExpected size: 57 but was: 0 in: [] within 10 seconds. org.kie.kogito.integrationtests.quarkus.ProcessEventIT.testSaveTaskjava.util.concurrent.TimeoutExceptionat java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960) at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095) at org.kie.kogito.integrationtests.quarkus.ProcessEventIT.testSaveTask(ProcessEventIT.java:200) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) |
fjtirado
force-pushed
the
incubator-kie-issues#1457
branch
from
e3735f1
to
7a75190
Compare
|
PR job Reproducerbuild-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 #3654 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3654/5/display/redirect Test results:
Those are the test failures: org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishEmptyEventsCollectionMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): userTasksEventsEmitter, processInstanceEmitter, processDefinitionEventsEmitter, processInstancesEventsEmitter, userTaskEmitter, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testReactiveMessagingEventPublisher_publishMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstanceEmitter, processDefinitionEventsEmitter, userTasksEventsEmitter, processInstancesEventsEmitter, userTaskEmitter, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testGroupingMessagingEventPublisher_publishMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstanceEmitter, processInstancesEventsEmitter, decoratedMessage, processDefinitionEventsEmitter, userTasksEventsEmitter, userTaskEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishGroupingByChannelMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): decoratedMessage, processInstancesEventsEmitter, processInstanceEmitter, userTasksEventsEmitter, userTaskEmitter, processDefinitionEventsEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishToTopic_ExceptionHandlingMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): decoratedMessage, userTaskEmitter, processInstancesEventsEmitter, processDefinitionEventsEmitter, userTasksEventsEmitter, processInstanceEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishMultipleEventsGroupedByChannelMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstancesEventsEmitter, processDefinitionEventsEmitter, userTasksEventsEmitter, processInstanceEmitter, userTaskEmitter, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishToTopicWithDecoratorMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): userTasksEventsEmitter, userTaskEmitter, decoratedMessage, processDefinitionEventsEmitter, processInstancesEventsEmitter, processInstanceEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testDecorateMessageMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): decoratedMessage, processInstanceEmitter, userTaskEmitter, processInstancesEventsEmitter, userTasksEventsEmitter, processDefinitionEventsEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testNoConsumersFoundMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): userTasksEventsEmitter, processInstancesEventsEmitter, processDefinitionEventsEmitter, userTaskEmitter, processInstanceEmitter, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. |
gmunozfe
force-pushed
the
incubator-kie-issues#1457
branch
from
a24217e
to
4cc1999
Compare
|
PR job Reproducerbuild-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 #3654 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3654/6/display/redirect Test results:
Those are the test failures: org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testNullEventInCollectionMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processDefinitionEventsEmitter, decoratedMessage, processInstanceConsumer, userTasksEventsEmitter, userTaskConsumer, processInstancesEventsEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishEmptyEventsCollectionMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processDefinitionEventsEmitter, userTaskConsumer, processInstanceConsumer, decoratedMessage, userTasksEventsEmitter, processInstancesEventsEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testReactiveMessagingEventPublisher_publishMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstancesEventsEmitter, processDefinitionEventsEmitter, userTaskConsumer, processInstanceConsumer, decoratedMessage, userTasksEventsEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testGroupingMessagingEventPublisher_publishMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstancesEventsEmitter, userTaskConsumer, userTasksEventsEmitter, processDefinitionEventsEmitter, decoratedMessage, processInstanceConsumer. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishUnsupportedEventTypeMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processDefinitionEventsEmitter, userTasksEventsEmitter, decoratedMessage, processInstancesEventsEmitter, userTaskConsumer, processInstanceConsumer. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishGroupingByChannelMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstancesEventsEmitter, userTasksEventsEmitter, processInstanceConsumer, processDefinitionEventsEmitter, userTaskConsumer, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishWithMultipleEventTypesSomeWithoutConsumersMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): userTaskConsumer, processInstanceConsumer, processInstancesEventsEmitter, processDefinitionEventsEmitter, userTasksEventsEmitter, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishToTopic_ExceptionHandlingMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstancesEventsEmitter, processDefinitionEventsEmitter, userTasksEventsEmitter, decoratedMessage, processInstanceConsumer, userTaskConsumer. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishMultipleEventsGroupedByChannelMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstanceConsumer, decoratedMessage, processDefinitionEventsEmitter, processInstancesEventsEmitter, userTasksEventsEmitter, userTaskConsumer. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testPublishToTopicWithDecoratorMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstancesEventsEmitter, userTaskConsumer, userTasksEventsEmitter, decoratedMessage, processInstanceConsumer, processDefinitionEventsEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testDecorateMessageMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstancesEventsEmitter, userTasksEventsEmitter, userTaskConsumer, processDefinitionEventsEmitter, processInstanceConsumer, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testEventsDisabledInConfigMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): userTasksEventsEmitter, processInstancesEventsEmitter, userTaskConsumer, processInstanceConsumer, decoratedMessage, processDefinitionEventsEmitter. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. org.kie.kogito.events.process.GroupingMessagingEventPublisherTest.testNoConsumersFoundMockito couldn't inject mock dependency on field 'private org.kie.kogito.events.process.AbstractMessagingEventPublisher$AbstractMessageEmitter org.kie.kogito.events.process.AbstractMessagingEventPublisher.processDefinitionConsumer' that is annotated with @Injectmocks in your test, because there were multiple matching mocks (i.e. fields annotated with @mock and having matching type): processInstanceConsumer, processInstancesEventsEmitter, processDefinitionEventsEmitter, userTasksEventsEmitter, userTaskConsumer, decoratedMessage. If you have multiple fields of same type in your class under test then consider naming the @mock fields identically to the respective class under test's fields, so Mockito can match them by name. |
gmunozfe
force-pushed
the
incubator-kie-issues#1457
branch
from
4cc1999
to
0d95589
Compare
fjtirado
commented
Sep 20, 2024
...ess/runtime/src/main/java/org/kie/kogito/events/process/GroupingMessagingEventPublisher.java
Outdated
Show resolved
Hide resolved
fjtirado
force-pushed
the
incubator-kie-issues#1457
branch
4 times, most recently
from
6f87c85
to
6b58fcd
Compare
|
PR job Reproducerbuild-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 #3654 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3654/11/display/redirect Test results:
Those are the test failures: org.kie.kogito.addon.quarkus.messaging.common.message.http.CloudEventHttpOutgoingDecoratorTest.verifyOutgoingHttpMetadataIsSetjava.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors[error]: Build step io.quarkus.arc.deployment.ArcProcessor#validate threw an exception: jakarta.enterprise.inject.spi.DeploymentException: Found 2 deployment problems: [1] Unsatisfied dependency for type io.quarkus.tls.TlsConfigurationRegistry and qualifiers [@default] - injection target: io.quarkus.reactivemessaging.http.runtime.QuarkusWebSocketConnector#tlsRegistry - declared on CLASS bean [types=[org.eclipse.microprofile.reactive.messaging.spi.ConnectorFactory, io.quarkus.reactivemessaging.http.runtime.QuarkusWebSocketConnector, org.eclipse.microprofile.reactive.messaging.spi.OutgoingConnectorFactory, org.eclipse.microprofile.reactive.messaging.spi.IncomingConnectorFactory, java.lang.Object], qualifiers=[@Any, @connector("quarkus-websocket")], target=io.quarkus.reactivemessaging.http.runtime.QuarkusWebSocketConnector] [2] Unsatisfied dependency for type io.quarkus.tls.TlsConfigurationRegistry and qualifiers [@default] - injection target: io.quarkus.reactivemessaging.http.runtime.QuarkusHttpConnector#tlsRegistry - declared on CLASS bean [types=[org.eclipse.microprofile.reactive.messaging.spi.ConnectorFactory, io.quarkus.reactivemessaging.http.runtime.QuarkusHttpConnector, org.eclipse.microprofile.reactive.messaging.spi.OutgoingConnectorFactory, org.eclipse.microprofile.reactive.messaging.spi.IncomingConnectorFactory, java.lang.Object], qualifiers=[@Any, @connector("quarkus-http")], target=io.quarkus.reactivemessaging.http.runtime.QuarkusHttpConnector] at io.quarkus.arc.processor.BeanDeployment.processErrors(BeanDeployment.java:1516) at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:320) at io.quarkus.arc.processor.BeanProcessor.initialize(BeanProcessor.java:160) at io.quarkus.arc.deployment.ArcProcessor.validate(ArcProcessor.java:488) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:849) at io.quarkus.builder.BuildContext.run(BuildContext.java:256) at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18) at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2513) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1538) at java.base/java.lang.Thread.run(Thread.java:840) at org.jboss.threads.JBossThread.run(JBossThread.java:501) Suppressed: jakarta.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type io.quarkus.tls.TlsConfigurationRegistry and qualifiers [@default] - injection target: io.quarkus.reactivemessaging.http.runtime.QuarkusWebSocketConnector#tlsRegistry - declared on CLASS bean [types=[org.eclipse.microprofile.reactive.messaging.spi.ConnectorFactory, io.quarkus.reactivemessaging.http.runtime.QuarkusWebSocketConnector, org.eclipse.microprofile.reactive.messaging.spi.OutgoingConnectorFactory, org.eclipse.microprofile.reactive.messaging.spi.IncomingConnectorFactory, java.lang.Object], qualifiers=[@Any, @connector("quarkus-websocket")], target=io.quarkus.reactivemessaging.http.runtime.QuarkusWebSocketConnector] at io.quarkus.arc.processor.Beans.resolveInjectionPoint(Beans.java:518) at io.quarkus.arc.processor.BeanInfo.init(BeanInfo.java:638) at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:308) ... 13 more Suppressed: jakarta.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type io.quarkus.tls.TlsConfigurationRegistry and qualifiers [@default] - injection target: io.quarkus.reactivemessaging.http.runtime.QuarkusHttpConnector#tlsRegistry - declared on CLASS bean [types=[org.eclipse.microprofile.reactive.messaging.spi.ConnectorFactory, io.quarkus.reactivemessaging.http.runtime.QuarkusHttpConnector, org.eclipse.microprofile.reactive.messaging.spi.OutgoingConnectorFactory, org.eclipse.microprofile.reactive.messaging.spi.IncomingConnectorFactory, java.lang.Object], qualifiers=[@Any, @connector("quarkus-http")], target=io.quarkus.reactivemessaging.http.runtime.QuarkusHttpConnector] at io.quarkus.arc.processor.Beans.resolveInjectionPoint(Beans.java:518) at io.quarkus.arc.processor.BeanInfo.init(BeanInfo.java:638) at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:308) ... 13 more |
fjtirado
force-pushed
the
incubator-kie-issues#1457
branch
2 times, most recently
from
9f062d8
to
2a219b7
Compare
fjtirado
commented
Sep 26, 2024
| @@ -52,7 +52,7 @@ | |||
| <version.io.quarkiverse.jackson-jq>2.0.2</version.io.quarkiverse.jackson-jq> | |||
| <version.io.quarkiverse.openapi.generator>2.4.1</version.io.quarkiverse.openapi.generator> | |||
| <version.io.quarkiverse.asyncapi>0.3.0</version.io.quarkiverse.asyncapi> | |||
| <version.io.quarkiverse.reactivemessaging.http>2.2.0</version.io.quarkiverse.reactivemessaging.http> | |||
| <version.io.quarkiverse.reactivemessaging.http>2.4.1</version.io.quarkiverse.reactivemessaging.http> | |||
There was a problem hiding this comment.
This is needed to include a fix on connector deserialization
ricardozanini
approved these changes
Sep 30, 2024
fjtirado
force-pushed
the
incubator-kie-issues#1457
branch
from
0105402
to
b8be950
Compare
rgdoliveira
pushed a commit
to rgdoliveira/kogito-runtimes
that referenced
this pull request
Oct 10, 2024
* [Fix apache/incubator-kie-issues#1457] Allow grouping of events * Add test for coverage * [Fix apache/incubator-kie-issues#1457] Grouping of event serialization * [Fix apache/incubator-kie-issues#1457] Adding default constructor * [Fix apache/incubator-kie-issues#1457] Adding TYPE constant --------- Co-authored-by: gmunozfe <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix apache/incubator-kie-issues#1457
Merge with apache/incubator-kie-kogito-examples#2017 and apache/incubator-kie-kogito-apps#2093