Pipeline: TestTaskRunRetry is flaky

Created on 28 Jul 2020  路  5Comments  路  Source: tektoncd/pipeline

All 5 comments

/assign @thomaschandler

@jlpettersson I wonder if this might be related to the garbage collection of failed pods. I'm unsure if GKE has a different garbage collection process than a self hosted k8s setup.

I'm thinking of updating TestTaskRunRetry to wait for pod state changes, at which point it will record the pod information for the failed pod, which can later be asserted once the PipelineRun is complete. Think this is worth a shot?

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

/remove-lifecycle stale

Was this page helpful?
0 / 5 - 0 ratings