Skip to content

Bump to Go 1.19#245

Merged
rhatdan merged 1 commit intoopenshift:masterfrom
nalind:update-update-update
Feb 8, 2023
Merged

Bump to Go 1.19#245
rhatdan merged 1 commit intoopenshift:masterfrom
nalind:update-update-update

Conversation

@nalind
Copy link
Copy Markdown
Member

@nalind nalind commented Feb 6, 2023

Use Go 1.19 instead of 1.16 in go.mod.
Test with 1.19/1.20 in Travis instead of 1.17/1.18. Bump the Travis environment from the default (16.04) to jammy (22.04), which is the latest currently available in Travis.
Update assorted direct dependencies.

Obsoletes #241.

Update conformance tests nonroot-USER-before-WORKDIR-notused and nonroot-USER-before-WORKDIR-used to request that they be built with BuildKit. Many conformance tests fail if we make this the default; we'll have to make that change and fix those later.

@nalind nalind changed the title Bump to Go 1.19 WIP: bump to Go 1.19 Feb 6, 2023
@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 Feb 6, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 6, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nalind

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Feb 6, 2023
@nalind
Copy link
Copy Markdown
Member Author

nalind commented Feb 6, 2023

I will be surprised if this passes without openshift/release#36040.

Well, I'm surprised.

@nalind nalind force-pushed the update-update-update branch from 28c2b6c to 6983ccd Compare February 6, 2023 16:36
@rhatdan
Copy link
Copy Markdown
Contributor

rhatdan commented Feb 6, 2023

LGTM

@nalind nalind force-pushed the update-update-update branch 8 times, most recently from 8fa2bb3 to a341f97 Compare February 6, 2023 20:19
@nalind
Copy link
Copy Markdown
Member Author

nalind commented Feb 7, 2023

Hmm, updating to docker 23.0.0 apparently doesn't result in API calls getting BuildKit by default after all. It must be a client default that changed.

@rhatdan
Copy link
Copy Markdown
Contributor

rhatdan commented Feb 7, 2023

@flouthoc WDYT?

@flouthoc
Copy link
Copy Markdown
Contributor

flouthoc commented Feb 7, 2023

Hmm, updating to docker 23.0.0 apparently doesn't result in API calls getting BuildKit by default after all. It must be a client default that changed.

Is this a recent change in docker 23.0.0 ? the PR LGTM. @nalind I think this already includes the needed change which I added here #246 hence closing #246

@nalind
Copy link
Copy Markdown
Member Author

nalind commented Feb 7, 2023

Hmm, updating to docker 23.0.0 apparently doesn't result in API calls getting BuildKit by default after all. It must be a client default that changed.

Is this a recent change in docker 23.0.0 ?

It's the first item called out in the "New" section in https://docs.docker.com/engine/release-notes/23.0/.

@rhatdan
Copy link
Copy Markdown
Contributor

rhatdan commented Feb 8, 2023

Since the tests pass is this ready to merge?

@nalind nalind force-pushed the update-update-update branch from a2398cf to f37fca8 Compare February 8, 2023 13:02
@nalind
Copy link
Copy Markdown
Member Author

nalind commented Feb 8, 2023

Since the tests pass is this ready to merge?

It was testing using a private fork of go-dockerclient to let the client request that the pair of cases that were failing be built using BuildKit instead, and I don't want us depending on my fork. Now that fsouza/go-dockerclient#961 is merged, we can avoid having to do that.

/retitle Bump to Go 1.19

@openshift-ci openshift-ci bot changed the title WIP: bump to Go 1.19 Bump to Go 1.19 Feb 8, 2023
@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 Feb 8, 2023
@nalind
Copy link
Copy Markdown
Member Author

nalind commented Feb 8, 2023

Also if anyone wants to approve openshift/release#36040, it's sure to save us some trouble later.

Use Go 1.19 instead of 1.16 in go.mod.
Test with 1.19/1.20 in Travis instead of 1.17/1.18.
Bump the Travis environment from the default (16.04) to jammy (22.04),
which is the latest currently available in Travis.
Update assorted direct dependencies.

Update conformance tests nonroot-USER-before-WORKDIR-notused and
nonroot-USER-before-WORKDIR-used to request that they be built with
BuildKit.  Many conformance tests fail if we make this the default;
we'll have to make that change and fix those later.

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
@nalind nalind force-pushed the update-update-update branch from f37fca8 to 91b1f3e Compare February 8, 2023 14:39
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 8, 2023

@nalind: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@rhatdan
Copy link
Copy Markdown
Contributor

rhatdan commented Feb 8, 2023

LGTM

@rhatdan rhatdan merged commit 93816b0 into openshift:master Feb 8, 2023
@nalind nalind deleted the update-update-update branch February 8, 2023 20:21
@nalind
Copy link
Copy Markdown
Member Author

nalind commented Feb 8, 2023

A reminder that this repository has a bot to handle merges.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants