Closed fbm3307 closed 3 weeks ago
@fbm3307: This pull request references SO-121 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-ovn-ipv6
Job Failure Risk Analysis for sha: aec0ec2a16e444772a07b263c6d458b93449349f
Job Name | Failure Risk |
---|---|
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6 | IncompleteTests Tests for this run (14) are below the historical average (1132): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node | Medium [sig-arch] events should not repeat pathologically for ns/openshift-etcd This test has passed 84.09% of 44 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node'] in the last 14 days. |
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial | Low [sig-arch] events should not repeat pathologically for ns/openshift-etcd This test has passed 79.49% of 39 runs on release 4.16 [amd64 aws ovn serial single-node] in the last week. |
/test verify
/retest
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-ovn-ipv6
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: coreydaley, fbm3307
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest-required
Remaining retests: 0 against base HEAD 7a9d6c265c161e452626f62c1482f597440ad20d and 2 for PR HEAD a2b507b4aaf9e071d278e438a9facd7b643ea358 in total
/retest-required
Remaining retests: 0 against base HEAD 856924d2d599980592fe7f6adcdd68366a97e4e7 and 1 for PR HEAD a2b507b4aaf9e071d278e438a9facd7b643ea358 in total
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-ovn-ipv6
@fbm3307: 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-aws-ovn-single-node-serial | a2b507b4aaf9e071d278e438a9facd7b643ea358 | link | false | /test e2e-aws-ovn-single-node-serial |
ci/prow/e2e-aws-ovn-single-node-upgrade | a2b507b4aaf9e071d278e438a9facd7b643ea358 | link | false | /test e2e-aws-ovn-single-node-upgrade |
ci/prow/e2e-gcp-ovn-rt-upgrade | a2b507b4aaf9e071d278e438a9facd7b643ea358 | link | false | /test e2e-gcp-ovn-rt-upgrade |
Full PR test history. Your PR dashboard.
Job Failure Risk Analysis for sha: a2b507b4aaf9e071d278e438a9facd7b643ea358
Job Name | Failure Risk |
---|---|
pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade | IncompleteTests Tests for this run (27) are below the historical average (573): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
/retest-required
Remaining retests: 0 against base HEAD ef0a1a09309e00e53dbe0eb808d308ad19d26d2e and 0 for PR HEAD a2b507b4aaf9e071d278e438a9facd7b643ea358 in total
/skip
Would it make sense to backport these changes in 4.15 or I misunderstood the problem?.
This required for the release process of samples operator for ocp4.16