Anton Gilgur
Anton Gilgur
@Joibel do you think you could take a look at this case of the issue as well?
TaskResult reconciliation should already be completed. In your issue, I'm pretty sure the ArtifactGC Pod _itself_ fails (due to the architecture). As it failed, the Controller cannot be sure that...
> I'm pretty sure the ArtifactGC Pod _itself_ fails (due to the architecture) Hmm, no, ArtifactGC can run on `arm64`; your Pod that fails due to arch is the `argosay`...
> I raised this PR because my workflow failed and no artifact was generated, so there is no need to do GC. Yes, the second half of [my previous comment](https://github.com/argoproj/argo-workflows/pull/13500#issuecomment-2308383109)...
Ok this makes more sense now given your [last comment on the issue](https://github.com/argoproj/argo-workflows/issues/13499#issuecomment-2308451871), thanks again for elaborating! From my [first comment above](https://github.com/argoproj/argo-workflows/pull/13500#pullrequestreview-2258675551) though: > A length of `0` could also...
> so I'd be okay to remove the `anyPodSuccess` altogether if it makes the code simpler. @juliev0 did you see my comment [above](https://github.com/argoproj/argo-workflows/pull/13500#issuecomment-2308636365)? I thought the check might be to...
@chengjoey that's when using `depends`, while OP is using `dependencies`. OP could use `depends` as a workaround here. But the fact that the `dependencies` variant succeeds does indeed seem like...
Ah because you have no task after task-two, so you wouldn't be able to use `.Failed` in `depends` per se. Or, you could use another workaround if you added a...
I'm wondering if this might partially help with #11354 and #12572 too 🤔
Yea same root cause as #12993, so let's consolidate the two Also, for back-link reference, this issue's title refers to #12103. https://github.com/argoproj/argo-workflows/issues/12103#issuecomment-1914589634 refers to an OOM as well, but unclear...