Open ianbenlolo opened 2 weeks ago
@ianbenlolo set_retry
is not working even without nested pipelines, see #9950 , I've also tried it without nested pipelines. It doesn't reties even once based on this spec:
tasks:
fail-job:
cachingOptions:
enableCache: true
componentRef:
name: comp-fail-job
dependentTasks:
- print-op1
retryPolicy:
backoffDuration: 0s
backoffFactor: 2.0
backoffMaxDuration: 3600s
maxRetryCount: 2
taskInfo:
name: fail-job
I didn't try with vertexAI, but I guess set_retry
is also not supported by VertexAI yet, see https://issuetracker.google.com/issues/226569351
@Faakhir30 Please see my comment in the original thread. It works for me on vertex ai. The issue is pipelines-in-pipelines that do not.
Environment
Steps to reproduce
In the docs here it says "Pipelines can themselves be used as components in other pipelines, just as you would use any other single-step component in a pipeline".
I was testing this out to see if a pipeline within a pipeline can be retried but i can't get it to work. Here is what I've tried (based on this.)
The fail_job will retry, but the pipeline-in-pipeline does not. Am i wrong in my thinking?
Expected result
The pipeline-in-pipeline should retry as well.
This is related to my discussion here but making an issue for visibility.
Impacted by this bug? Give it a 👍.