Improve test stability

[SaschaSchwarze0]

Changes

PR Use GitHub action for e2e test #611 should not have been merged by the robot. It had an approval, but the tests were not successful.

Basically, after having added the fourth Kubernetes version to the test matrix, the actions became unstable. Statements in the documentation like this leave room for interpretation, but I assume there is some resource limit and CPU is becoming the bottleneck.

I am therefore trying to limit the parallelism.

In addition, I am making changes to remove race conditions:

• in e2e, I am waiting for the Build to be registered before creating a BuildRun
• in integration, I am waiting for the Build to have a registration before creating a BuildRun
• in integration, after creating a namespace, I am waiting for the default service account to exist and contain the token secret
• in integration, I added a polling to wait for the owner updates to happen
• in integration, I commented our a part where a test case assumed to see a Pending TaskRun and BuildRun

Finally, I have to disable the runs with more than one Kubernetes version. The reason is that I see intermittent API calls (performed by the test code) failing with etcdserver: request timed out. We have some retry behavior for them for get calls in e2e, but not for creations and updates. And we have no retry as of now in integration. I am mainly seeing it for creations (namespace, clusterbuildstrategy) in integration.

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Release notes block has been filled in, or marked NONE

Release Notes

NONE

[qu1queee]

@SaschaSchwarze0 thanks, nice!
/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qu1queee]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment