Custom task condition doesn't generate status result in some cases

/kind bug

What steps did you take and what happened: The below example doesn’t generate the condition status for the first custom task.

from kfp import dsl
from kfp_tekton.tekton import CEL_ConditionOp


@dsl.pipeline("example-ab")
def example_ab(num: int = 42):
  isNumZero = CEL_ConditionOp(f"{num} == 0").output
  zero = CEL_ConditionOp(f"0").output

@dsl.pipeline("example-ba")
def example_ba(num: int = 42):
  zero = CEL_ConditionOp(f"0").output
  isNumZero = CEL_ConditionOp(f"{num} == 0").output

def main():
  from kfp_tekton.compiler import TektonCompiler as Compiler
  Compiler().compile(example_ab, __file__.replace('.py', '-ab.yaml'))
  Compiler().compile(example_ba, __file__.replace('.py', '-ba.yaml'))

if __name__ == '__main__':
  main()

outputs: Note that the first cel-condition custom task didn’t generate the condition statement as status.

spec:
  params:
  - name: num
    value: '42'
  pipelineSpec:
    params:
    - name: num
      default: '42'
    tasks:
    - name: cel-condition
      taskRef:
        name: cel_condition
        apiVersion: cel.tekton.dev/v1alpha1
        kind: CEL
    - name: cel-condition-2
      params:
      - name: status
        value: $(params.num) == 0
      taskRef:
        name: cel_condition
        apiVersion: cel.tekton.dev/v1alpha1
        kind: CEL
  timeout: 0s

What did you expect to happen:

Additional information: [Miscellaneous information that will assist in solving the issue.]

Environment:

• Python Version (use python --version):
• SDK Version:
• Tekton Version (use tkn version):
• Kubernetes Version (use kubectl version):
• OS (e.g. from /etc/os-release):

[Tomcli]

@Udiknedormin I reverted back to 6adfcc64f3c4deb0a90411b9f72347d6cc418e6d but still don’t see this issue. Probably it happened when it was in the old PR stage. Since then, I did some bug fixes on the custom task such as fixing the regex on parameter mapping b74d4a5cbf71fbe64677cf55693973a48a6b669c.

[google-oss-robot]

@Tomcli: Closing this issue.

In response to this:

/close reopen it if this issue still exist

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.