[ISSUE] Turn off automatic test retries

[jessesimpson36]

Describe the issue:

Automatic test retries have lately been a pain, because the following will happen.

1. I start working on a CI workflow, and it crashes.
2. I make a fix and push it.
3. The commit with the fix is running CI
4. The commit prior to the fix starts a retry
5. The commit with the fix has it's CI cancelled because the timestamp of the retry is newer than the timestamp of the newer commit.

We don't need to remove the capability to retry, lets just adjust the retry count to 1 or 0.

If for whatever reason, you get a CI test failure for some arbitrary reason like a network failure, you can click the Retry button, or add an empty commit.

Actual behavior:

Expected behavior:

How to reproduce:

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

• Platform:
• Helm CLI version:
• Chart version:
• Values file:

[eamonnmoloney]

What is the root cause the leads to failures? I've been burned by this too many times and so far the only issue I see comes from resource constraints or network failures.

I don't see those cases as valid reasons to have an auto retry. Manual retry would be safer and sufficient in my view.

The resource issue actually is a serious problem and should never be a retry fix. The resource scaling needs to be fixed. The network issues I've seen are github issues, which is not something I think we should work around.

[jessesimpson36]

We should check if the PR #4649
fixes this issue (or helps in some way).

[clementnero]

We should check if the PR #4649
fixes this issue (or helps in some way).

The change will definitely help reduce the likelihood of race conditions.

@jessesimpson36 The issue should be fully addressed with camunda/infra-global-github-actions#538.