Measure container restarts over an interval instead of absolute

[smarterclayton]

We run these tests after disruptive events where restarts are
necessary. Instead of looking at absolute restart count, capture
the number of initial restarts and then compare subsequent runs
to ensure the count is smaller. We double the time interval and
halve the number of failing restarts in order to ensure we capture
slow restart failures (full backoff is 5m, but we can catch slow
but not limited backoff).

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• test/extended/OWNERS [smarterclayton]

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

[smarterclayton]

/retest

[wking]

images:

Warning: Pull failed, retrying in 5s ...
error: build error: failed to pull image: After retrying 2...501ab66378d954ee8617: unauthorized: authentication required

Dunno what that's about.

[smarterclayton]

/retest

[smarterclayton]

/retest

[hexfusion]

/test e2e-gcp-upgrade

[hexfusion]

fips

Jun 16 14:53:01.193 E ns/e2e-test-build-webhooks-d2ph5 pod/pushbuild-1-build node/ip-10-0-190-41.us-west-1.compute.internal container/git-clone container exited with code 1 (Error): Cloning "http://my.docker/build" ...\nerror: fatal: unable to access 'http://my.docker/build/': Could not resolve host: my.docker; Unknown error\n

https://search.apps.build01.ci.devcluster.openshift.com/?search=fatal%3A+unable+to+access+%27http%3A%2F%2Fmy.docker&maxAge=48h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job

[smarterclayton]

GCP passed, going to mark this green to unblock e2e-aws-disruptive

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[hexfusion]

/retest

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[hexfusion]

/cherry-pick release-4.5

[openshift-cherrypick-robot]

@hexfusion: new pull request created: #25152

Details

In response to this:

/cherry-pick release-4.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@hexfusion: failed to push cherry-picked changes in GitHub: pushing failed, output: "To https://github.com/openshift-cherrypick-robot/origin\n ! [rejected] cherry-pick-25115-to-release-4.5 -> cherry-pick-25115-to-release-4.5 (fetch first)\nerror: failed to push some refs to 'https://openshift-cherrypick-robot:CENSORED@github.com/openshift-cherrypick-robot/origin'\nhint: Updates were rejected because the remote contains work that you do\nhint: not have locally. This is usually caused by another repository pushing\nhint: to the same ref. You may want to first integrate the remote changes\nhint: (e.g., 'git pull ...') before pushing again.\nhint: See the 'Note about fast-forwards' in 'git push --help' for details.\n", error: exit status 1

Details

In response to this:

/cherrypick release-4.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[hexfusion]

/cherry-pick release-4.4

[openshift-cherrypick-robot]

@hexfusion: #25115 failed to apply on top of branch "release-4.4":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	test/extended/operators/cluster.go
M	test/extended/util/annotate/generated/zz_generated.annotations.go
Falling back to patching base and 3-way merge...
Auto-merging test/extended/util/annotate/generated/zz_generated.annotations.go
CONFLICT (content): Merge conflict in test/extended/util/annotate/generated/zz_generated.annotations.go
Auto-merging test/extended/operators/cluster.go
CONFLICT (content): Merge conflict in test/extended/operators/cluster.go
Patch failed at 0001 Measure container restarts over an interval instead of absolute

Details

In response to this:

/cherry-pick release-4.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.