origin
origin copied to clipboard
test/extended/scheduling/pods: Non-fatal different-nodes flake for 4.10 and earlier
The separation is only reliable on 4.11 and later. Still test on earlier releases, but only report violations as non-fatal flakes for those older releases.
Like #27053, but with a new JobType.HasCompleted helper, more robust version comparison, and a flake instead of a silent success when run on versions where the test-cases are not expected to reliably succeed.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: wking
To complete the pull request process, please assign smarterclayton after the PR has been reviewed.
You can assign the PR to them by writing /assign @smarterclayton in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
There was no error output from the command.
[ERROR] hack/lib/cmd.sh:10: `return "${return_code}"` exited with status 1.
[ERROR] hack/verify-generated.sh exited with code 1 after 00h 00m 39s
Not all that helpful. Maybe a flake?
/test verify
/test verify
Now that #27060 has landed to make the output more useful.
Hrm:
panic: unable to find test [Top Level] [sig-scheduling][Early] The HAProxy router pods should be scheduled on different nodes
Presumably because of 40ec84a38a0660. How do I make both the actual test runs and the verify presubmit happy at the same time?
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@wking: PR needs rebase.
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.
@wking: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-gcp-builds | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-builds |
| ci/prow/e2e-gcp | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp |
| ci/prow/e2e-gcp-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-upgrade |
| ci/prow/e2e-gcp-csi | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-gcp-csi |
| ci/prow/e2e-aws-csi | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-csi |
| ci/prow/e2e-aws-serial | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-serial |
| ci/prow/e2e-aws-fips | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-fips |
| ci/prow/e2e-agnostic-cmd | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-agnostic-cmd |
| ci/prow/e2e-gcp-ovn-rt-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-gcp-ovn-rt-upgrade |
| ci/prow/e2e-aws-cgroupsv2 | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-cgroupsv2 |
| ci/prow/e2e-aws-single-node | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-single-node |
| ci/prow/e2e-aws-single-node-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-single-node-upgrade |
| ci/prow/e2e-aws-ovn-fips | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-ovn-fips |
| ci/prow/e2e-gcp-ovn | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-ovn |
| ci/prow/e2e-gcp-ovn-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-ovn-upgrade |
| ci/prow/e2e-aws-ovn-serial | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-ovn-serial |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
@wking: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-gcp-builds | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-builds |
| ci/prow/e2e-gcp | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp |
| ci/prow/e2e-gcp-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-upgrade |
| ci/prow/e2e-gcp-csi | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-gcp-csi |
| ci/prow/e2e-aws-csi | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-csi |
| ci/prow/e2e-aws-serial | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-serial |
| ci/prow/e2e-aws-fips | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-fips |
| ci/prow/e2e-agnostic-cmd | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-agnostic-cmd |
| ci/prow/e2e-gcp-ovn-rt-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-gcp-ovn-rt-upgrade |
| ci/prow/e2e-aws-cgroupsv2 | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-cgroupsv2 |
| ci/prow/e2e-aws-single-node | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-single-node |
| ci/prow/e2e-aws-single-node-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | false | /test e2e-aws-single-node-upgrade |
| ci/prow/e2e-aws-ovn-fips | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-ovn-fips |
| ci/prow/e2e-gcp-ovn | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-ovn |
| ci/prow/e2e-gcp-ovn-upgrade | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-ovn-upgrade |
| ci/prow/e2e-aws-ovn-serial | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-ovn-serial |
| ci/prow/unit | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test unit |
| ci/prow/e2e-gcp-ovn-image-ecosystem | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-ovn-image-ecosystem |
| ci/prow/e2e-gcp-ovn-builds | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-gcp-ovn-builds |
| ci/prow/e2e-aws-ovn-image-registry | 40ec84a38a06600c383ae6c2f415b4685cecfff9 | link | true | /test e2e-aws-ovn-image-registry |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.