Closed MiguelPires closed 3 years ago
[Expected all columns to be empty] Expecting empty but was: [JOBS, JOB_STATES, JOB_ACTIVATABLE]
.
So a job still existed. Looking at the Logs, it contains the following sequence:
13:39:12.384 [] INFO io.zeebe.test.records - {"valueType":"JOB","key":-1,"position":21,"timestamp":1611841141864,"recordType":"COMMAND","intent":"CREATE","partitionId":1,"rejectionType":"NULL_VAL","rejectionReason":"","brokerVersion":"0.27.0","sourceRecordPosition":18,"value":{"deadline":-1,"variables":{},"errorMessage":"","type":"test","workflowInstanceKey":2251799813685251,"bpmnProcessId":"workflow","workflowKey":2251799813685249,"elementId":"task","elementInstanceKey":2251799813685256,"retries":3,"customHeaders":{},"worker":"","workflowDefinitionVersion":1,"errorCode":""}}
13:39:12.385 [] INFO io.zeebe.test.records - {"valueType":"WORKFLOW_INSTANCE","key":2251799813685256,"position":22,"timestamp":1611841141870,"recordType":"EVENT","intent":"ELEMENT_TERMINATING","partitionId":1,"rejectionType":"NULL_VAL","rejectionReason":"","brokerVersion":"0.27.0","sourceRecordPosition":19,"value":{"version":1,"flowScopeKey":2251799813685251,"workflowInstanceKey":2251799813685251,"bpmnProcessId":"workflow","workflowKey":2251799813685249,"elementId":"task","bpmnElementType":"SERVICE_TASK","parentWorkflowInstanceKey":-1,"parentElementInstanceKey":-1}}
13:39:12.385 [] INFO io.zeebe.test.records - {"valueType":"JOB","key":2251799813685260,"position":23,"timestamp":1611841141872,"recordType":"EVENT","intent":"CREATED","partitionId":1,"rejectionType":"NULL_VAL","rejectionReason":"","brokerVersion":"0.27.0","sourceRecordPosition":21,"value":{"deadline":-1,"variables":{},"errorMessage":"","type":"test","workflowInstanceKey":2251799813685251,"bpmnProcessId":"workflow","workflowKey":2251799813685249,"elementId":"task","elementInstanceKey":2251799813685256,"retries":3,"customHeaders":{},"worker":"","workflowDefinitionVersion":1,"errorCode":""}}
13:39:12.386 [] INFO io.zeebe.test.records - {"valueType":"WORKFLOW_INSTANCE","key":2251799813685256,"position":24,"timestamp":1611841141879,"recordType":"EVENT","intent":"ELEMENT_TERMINATED","partitionId":1,"rejectionType":"NULL_VAL","rejectionReason":"","brokerVersion":"0.27.0","sourceRecordPosition":22,"value":{"version":1,"flowScopeKey":2251799813685251,"workflowInstanceKey":2251799813685251,"bpmnProcessId":"workflow","workflowKey":2251799813685249,"elementId":"task","bpmnElementType":"SERVICE_TASK","parentWorkflowInstanceKey":-1,"parentElementInstanceKey":-1}}
Now this is using the never released broker version 0.27.0
(and looking at the date, seems to have occurred around the time of 1.0.0-alpha1
). Back then, jobs were still created and cancelled by job commands, ie. Job:Create
, Job:Cancel
(note the Job:Create
command in the sequence above). However, we don't see a Job:Cancel
appear anywhere in the logs although the process successfully completes. Looking deeper at that code, it seems that the following happened:
To me this sounds like a bug (state garbage) that no longer exists. (jobs are created synchronously: create and cancel commands no longer exist)
I've also let the current version of this test ProcessExecutionCleanStateTest#testProcessWithEventSubprocess
run ~1000 times successfully locally. Let's close this.
Summary
Seldom (at least I haven't seen it before)
No.
Based on the assertion it might simply be a condition that took too long to be met but I didn't look into it.
Failures
Assertion failure
Logs
https://ci.zeebe.camunda.cloud/blue/organizations/jenkins/zeebe-io%2Fzeebe/detail/staging/2780/tests
Logs