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

Dockerfile*: Bump to Go 1.14 #414

Merged
merged 2 commits into from Jul 24, 2020
Merged

Conversation

wking
Copy link
Member

@wking wking commented Jul 22, 2020

Other components have already moved, such as the installer in openshift/installer@46a5f49709 (openshift/installer#3723). This will make enforcing Go 1.14 formatting more consistent, per discussion here.

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2020
Other components have already moved, such as the installer in
openshift/installer@46a5f49709 (bump the minimum version for building
installer to go 1.14, 2020-06-04, openshift/installer#3723).  This
will make enforcing Go 1.14 formatting more consistent, per discussion
in [1].

[1]: https://github.com/openshift/cluster-version-operator/pull/411/files#r458821597
Generated with:

  $ go mod vendor

using:

  $ go version
  go version go1.14.4 linux/amd64

addressing [1]:

  Building github.com/openshift/cluster-version-operator (v1.0.0-302-g13e97af4-dirty)
  # golang.org/x/text/unicode/norm
  vendor/golang.org/x/text/unicode/norm/composition.go:466:2: undefined: recompMapOnce
  ...

I'd guessed these slipped through in 2021b86 (Bug 1855577: Updating
the golang.org/x/text version to v0.3.3, 2020-07-15, openshift#408).

  $ go1.13.5 mod vendor

pulls them in too, so I'm not entirely clear on how they slipped
through.  But they seem to be fatal for 1.14 builds and non-fatal for
1.13 builds.

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-version-operator/414/pull-ci-openshift-cluster-version-operator-master-images/1286049697189859328
@wking
Copy link
Member Author

wking commented Jul 23, 2020

Unrelated PDB disruption.

Copy link
Member

@LalatenduMohanty LalatenduMohanty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 23, 2020
@LalatenduMohanty
Copy link
Member

/test e2e-upgrade

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty, wking

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:
  • OWNERS [LalatenduMohanty,wking]

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

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@wking
Copy link
Member Author

wking commented Jul 23, 2020

All of the last five update tests died on Application behind service load balancer with PDB is not disrupted. Should we /override? I can't see how a CVO pivot to 1.14 would be related.

@vrutkovs
Copy link
Member

+1 to override

@sdodson
Copy link
Member

sdodson commented Jul 23, 2020

/override ci/prow/e2e-upgrade

@openshift-ci-robot
Copy link
Contributor

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-upgrade

In response to this:

/override ci/prow/e2e-upgrade

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.

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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants