search

openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.44k stars 4.69k forks source link

[release-4.15]: OCPBUGS-32554: Also rely on oomkilled exit code 137 in build test #28724

Closed ardaguclu closed 3 weeks ago

ardaguclu commented 3 weeks ago

This should be a manual cherry-pick of https://github.com/openshift/origin/pull/28725, although the reverse is true (because issues are only happening on 4.15). In any case, these two PRs should be identical.

ardaguclu commented 3 weeks ago

/retest-required

openshift-ci[bot] commented 3 weeks ago

@ardaguclu: 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-etcd-recovery 9049131cbd40d68b7a03ea289c2a2bd35623b7cb link false /test e2e-aws-etcd-recovery
ci/prow/e2e-aws-ovn-single-node-upgrade 9049131cbd40d68b7a03ea289c2a2bd35623b7cb link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial 9049131cbd40d68b7a03ea289c2a2bd35623b7cb link false /test e2e-aws-ovn-single-node-serial

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci[bot] commented 3 weeks ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, soltysh

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: - ~~[test/OWNERS](https://github.com/openshift/origin/blob/release-4.15/test/OWNERS)~~ [soltysh] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci-robot commented 3 weeks ago

@ardaguclu: This pull request references Jira Issue OCPBUGS-32554, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/origin/pull/28724): >This should be a manual cherry-pick of https://github.com/openshift/origin/pull/28725, although the reverse is true (because issues are only happening on 4.15). In any case, these two PRs should be identical. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
ardaguclu commented 3 weeks ago

/jira refresh

openshift-ci-robot commented 3 weeks ago

@ardaguclu: This pull request references Jira Issue OCPBUGS-32554, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to [this](https://github.com/openshift/origin/pull/28724#issuecomment-2069666504): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
ardaguclu commented 3 weeks ago

/jira refresh

openshift-ci-robot commented 3 weeks ago

@ardaguclu: This pull request references Jira Issue OCPBUGS-32554, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to [this](https://github.com/openshift/origin/pull/28724#issuecomment-2069672148): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
sayan-biswas commented 3 weeks ago

/label cherry-pick-approved

openshift-ci[bot] commented 3 weeks ago

@sayan-biswas: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]

In response to [this](https://github.com/openshift/origin/pull/28724#issuecomment-2071617994): >/label cherry-pick-approved Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
kasturinarra commented 3 weeks ago

/label cherry-pick-approved

ardaguclu commented 3 weeks ago

/jira refresh

openshift-ci-robot commented 3 weeks ago

@ardaguclu: This pull request references Jira Issue OCPBUGS-32554, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.15.z) matches configured target version for branch (4.15.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * release note type set to "Release Note Not Required" * dependent bug [Jira Issue OCPBUGS-32477](https://issues.redhat.com//browse/OCPBUGS-32477) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-32477](https://issues.redhat.com//browse/OCPBUGS-32477) targets the "4.16.0" version, which is one of the valid target versions: 4.16.0 * bug has dependents
In response to [this](https://github.com/openshift/origin/pull/28724#issuecomment-2076872496): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci-robot commented 3 weeks ago

@ardaguclu: Jira Issue OCPBUGS-32554: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-32554 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/origin/pull/28724): >This should be a manual cherry-pick of https://github.com/openshift/origin/pull/28725, although the reverse is true (because issues are only happening on 4.15). In any case, these two PRs should be identical. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-bot commented 3 weeks ago

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.15.0-202404251108.p0.g9260d49.assembly.stream.el8 for distgit openshift-enterprise-tests. All builds following this will include this PR.