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

[Fix_3672] Process instance in Error state is not longer active #3373

Closed
wants to merge 1 commit into from

Conversation

fjtirado
Copy link
Contributor

Fixes #3372

@kie-ci3
Copy link
Contributor

kie-ci3 commented Jan 25, 2024

PR job #1 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer

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 #3373 --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-3373/1/display/redirect

Test results:

  • PASSED: 3325
  • FAILED: 14

Those are the test failures:

org.kie.persistence.filesystem.FileSystemProcessInstancesTest.testFindByIdReadMode No value present
org.kie.kogito.infinispan.CacheProcessInstancesIT.testFindByIdReadMode
Expected size: 1 but was: 0 in:
[]
org.kie.persistence.jdbc.OracleProcessInstancesIT.testMultipleProcesses
Expected size: 1 but was: 0 in:
[]
org.kie.persistence.jdbc.PostgreSqlProcessInstancesIT.testMultipleProcesses
Expected size: 1 but was: 0 in:
[]
org.kie.persistence.jdbc.PostgreSqlProcessInstancesLockIT.testMultipleProcesses
Expected size: 1 but was: 0 in:
[]
org.kie.kogito.mongodb.MongoDBProcessInstancesIT.testFindByIdReadModeWithTransaction
Expected size: 1 but was: 0 in:
[]
org.kie.kogito.mongodb.MongoDBProcessInstancesIT.testFindByIdReadMode
Expected size: 1 but was: 0 in:
[]
org.kie.persistence.postgresql.PostgresqlProcessInstancesIT.testMultipleProcesses
Expected size: 1 but was: 0 in:
[]
org.kie.persistence.postgresql.PostgresqlProcessInstancesWithLockIT.testMultipleProcesses
Expected size: 1 but was: 0 in:
[]
org.jbpm.bpmn2.ActivityTest.testUserTaskWithAssignment Could not find process instance for id 0c77e4c5-372a-4148-9de0-c01678a66e98
org.jbpm.bpmn2.canonical.ActivityGenerationModelTest.testExclusiveSplitRetriggerAfterError null source
org.kie.kogito.codegen.tests.PublishEventIT.testServiceTaskProcessWithError
Expected size: 1 but was: 2 in:
[ProcessInstanceStateDataEvent {specVersion=1.0, id='1b6669f5-7ee1-4fe4-825d-33bfe00a5cbc', source=http://myhost/ServiceProcessDifferentOperations, type='ProcessInstanceStateDataEvent', time=2024-01-25T13:33:57.271872662-05:00, subject='null', dataContentType='application/json', dataSchema=null, data=ProcessInstanceStateEventBody [eventDate=Thu Jan 25 13:33:57 EST 2024, eventUser=null, eventType=2, processId=ServiceProcessDifferentOperations, processVersion=1.0, processType=BPMN, processInstanceId=4b7897de-53fc-4207-9c9f-2613d576f600, businessKey=null, processName=Service Process, parentInstanceId=null, rootProcessId=null, rootProcessInstanceId=null, state=5, roles=null], kogitoProcessInstanceId='4b7897de-53fc-4207-9c9f-2613d576f600', kogitoRootProcessInstanceId='null', kogitoProcessId='ServiceProcessDifferentOperations', kogitoRootProcessId='null', kogitoAddons='test', kogitoIdentity='null', extensionAttributes={kogitoproctype=BPMN, kogitoprocinstanceid=4b7897de-53fc-4207-9c9f-2613d576f600, kogitoprocist=5, kogitoprocversion=1.0, kogitoprocid=ServiceProcessDifferentOperations, kogitoaddons=test}},
ProcessInstanceStateDataEvent {specVersion=1.0, id='4acd7dc4-369a-416e-b499-57d4deced604', source=http://myhost/ServiceProcessDifferentOperations, type='ProcessInstanceStateDataEvent', time=2024-01-25T13:33:57.273649616-05:00, subject='null', dataContentType='application/json', dataSchema=null, data=ProcessInstanceStateEventBody [eventDate=Thu Jan 25 13:33:57 EST 2024, eventUser=null, eventType=1, processId=ServiceProcessDifferentOperations, processVersion=1.0, processType=BPMN, processInstanceId=4b7897de-53fc-4207-9c9f-2613d576f600, businessKey=null, processName=Service Process, parentInstanceId=null, rootProcessId=null, rootProcessInstanceId=null, state=5, roles=null], kogitoProcessInstanceId='4b7897de-53fc-4207-9c9f-2613d576f600', kogitoRootProcessInstanceId='null', kogitoProcessId='ServiceProcessDifferentOperations', kogitoRootProcessId='null', kogitoAddons='test', kogitoIdentity='null', extensionAttributes={kogitoproctype=BPMN, kogitoprocinstanceid=4b7897de-53fc-4207-9c9f-2613d576f600, kogitoprocist=5, kogitoprocversion=1.0, kogitoprocid=ServiceProcessDifferentOperations, kogitoaddons=test}}]
org.kie.kogito.persistence.kafka.KafkaProcessInstancesIT.testFindByIdReadMode No value present
org.kie.kogito.quarkus.workflows.ExpressionRestIT.testExpressionOutputValidation 1 expectation failed.
JSON path id doesn't match.
Expected: not null
Actual: null

@fjtirado fjtirado closed this Jan 26, 2024
@fjtirado
Copy link
Contributor Author

Closing because forcing error to finish the process is not compatible with retrigger functionality, which is exposed in several existing endpoints. We need to reevaluate how the current implementation fits with straight trhough process

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.

Workflow instances that are in error should have their end date set
2 participants