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
NE-1490: update to go v1.20 #1012
NE-1490: update to go v1.20 #1012
Conversation
@candita: This pull request references NE-1490 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. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Skipping CI for Draft Pull Request. |
/test verify |
/jira refresh |
@candita: This pull request references NE-1490 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Interesting new failure:
/test e2e-gcp-operator |
/test e2e-aws-ovn-single-node
|
/test e2e-aws-ovn-single-node |
Timed out after 4 hours:
/test e2e-aws-ovn-single-node |
Thanks! I was curious whether/why Go 1.20 was required. In case anyone else is curious:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah 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 |
@candita: The following test failed, say
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. |
Cluster failures?
/test e2e-hypershift |
9c62f2b
into
openshift:master
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-ingress-operator-container-v4.16.0-202401110907.p0.g9c62f2b.assembly.stream for distgit ose-cluster-ingress-operator. |
Update to go v1.20