You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the case where the TaskRuns were unsuccessfully canceled, the pipelineRun should not be canceled with Succedded state.
Thanks to Lee's comment as below:
It seems like this test is expecting that the taskruns referenced in the pipelineruns aren't able to be canceled successfully, and therefore the PipelineRun can't be canceled. However, what's actually happening is that the PipelineRun is canceled successfully. It sounds like our cancelation logic doesn't handle childReferences correctly.
JeromeJu
changed the title
Cancel shouldn't succeed for TaskRuns with minimal EmbeddedStatus
Canceled PipelineRun shouldn't succeed for failed-to-Cancel TaskRuns with minimal EmbeddedStatus
Jan 13, 2023
I tried to recreate one of the other test failures from your PR, TestReconcileOnCancelledRunFinallyPipelineRunWithRunningFinalTask, using the following definitions:
I waited until the taskrun was complete, and then updated the PipelineRun status with "CancelledRunFinally". With both full and minimal embedded-status, the PipelineRun ended up with the correct taskruns/childrefs in its status.
So I checked out your changes in #5934 and was able to fix the test cases by changing the TaskRuns in the PipelineRun status in the test cases to ChildRefs. I think this may be an issue with the PR rather than a bug-- sorry I got this one wrong. If you do find a reliable reproducer, definitely feel free to reopen this issue!
Expected Behavior
For the case where the TaskRuns were unsuccessfully canceled, the pipelineRun should not be canceled with Succedded state.
Thanks to Lee's comment as below:
It seems like this test is expecting that the taskruns referenced in the pipelineruns aren't able to be canceled successfully, and therefore the PipelineRun can't be canceled. However, what's actually happening is that the PipelineRun is canceled successfully. It sounds like our cancelation logic doesn't handle childReferences correctly.
Originally posted by @lbernick in #5934 (comment)
Actual Behavior
The TaskRun was cancelled while the PipelineRun was succeedded under
minimal
EmbeddedStatus.
Steps to Reproduce the Problem
Minimal
EmbeddedStatus
tkn pr <pr name> cancel
Additional Info
The text was updated successfully, but these errors were encountered: