taskrunCancelled
sets the startedAt
and finishedAt
times for steps that were not executed
#8479
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Expected Behavior
When a taskRun is cancelled due to a timeout, I expect the steps that were not executed to have no timings attached to them. It is misleading to set the same time for all steps, as steps are generally executed in sequence. Additionally, the startedAt time is set to the start time of the taskRun. Meaning, if a taskRun is canceled while executing the second step of a task, that step may have a startedAt time earlier than the first step, which is inaccurate.
Actual Behavior
Steps to Reproduce the Problem
Apply this
pipelineRun
:Analyze the
taskRun
:Analyze the steps:
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
The text was updated successfully, but these errors were encountered: