Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use centos:stream9 and golang1.19 #1369

Closed
wants to merge 1 commit into from

Conversation

soltysh
Copy link

@soltysh soltysh commented Sep 19, 2022

No description provided.

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Sep 19, 2022
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 19, 2022
@openshift-ci-robot
Copy link

@soltysh: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Sep 19, 2022
@openshift-ci
Copy link

openshift-ci bot commented Sep 19, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 19, 2022
@soltysh
Copy link
Author

soltysh commented Sep 19, 2022

/test e2e-gcp

@openshift-ci-robot
Copy link

@soltysh: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@soltysh: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@soltysh
Copy link
Author

soltysh commented Sep 19, 2022

/remove-label backports/unvalidated-commits
/label backports/validated-commits

@openshift-ci openshift-ci bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Sep 19, 2022
@soltysh soltysh changed the title [WIP] Dockerfile: use centos:stream9 Use centos:stream9 and golang1.19 Sep 19, 2022
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 19, 2022
@kikisdeliveryservice
Copy link

kikisdeliveryservice commented Sep 19, 2022

The bot reverted your change in release again 😭

@kikisdeliveryservice
Copy link

kikisdeliveryservice commented Sep 19, 2022

The go bump is causing this PR to fail verify. I'm sure it's the go bump bc a PR that only changes centos passes the very same job.

Solution: 1) we can fix this PR so we don't break verify in our repo or 2) use the centos-only PR here and deal with go bump separately.

After centos is merged via either pr we will also need: openshift/release#32425

@openshift-ci
Copy link

openshift-ci bot commented Sep 19, 2022

@soltysh: 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-upgrade 1cb2ee6 link true /test e2e-gcp-upgrade
ci/prow/e2e-aws-serial 1cb2ee6 link true /test e2e-aws-serial
ci/prow/e2e-azure-upgrade 1cb2ee6 link true /test e2e-azure-upgrade
ci/prow/e2e-aws-upgrade 1cb2ee6 link true /test e2e-aws-upgrade
ci/prow/verify 1cb2ee6 link true /test verify
ci/prow/e2e-aws-cgroupsv2 1cb2ee6 link true /test e2e-aws-cgroupsv2

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants