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

Update to go-1.21 #4139

Merged
merged 4 commits into from
May 23, 2024
Merged

Update to go-1.21 #4139

merged 4 commits into from
May 23, 2024

Conversation

praveenkumar
Copy link
Member

No description provided.

update-go-version.sh Outdated Show resolved Hide resolved
update-go-version.sh Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
.github/workflows/make-check.yml Outdated Show resolved Hide resolved
@praveenkumar
Copy link
Member Author

/retest

Makefile Outdated Show resolved Hide resolved
@cfergeau
Copy link
Contributor

cfergeau commented May 3, 2024

mak echeck failed on Windows.

@praveenkumar
Copy link
Member Author

make check failed on Windows.

@cfergeau only on windows-2019 and windows-2022 it is working as expected, I will check what's is happening there.

Copy link
Contributor

@cfergeau cfergeau left a comment

Choose a reason for hiding this comment

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

Fwiw, we used to have a similar workaround 1b6bf222090f
I don't know what "win-2022 also have OS-10.0.x build" means.

@praveenkumar
Copy link
Member Author

Fwiw, we used to have a similar workaround 1b6bf222090f

Do you suggest that we should use a hack keep the windows-2019 runner job?

I don't know what "win-2022 also have OS-10.0.x build" means.

I took it that it have some similarity with win-10 but as per https://en.wikipedia.org/wiki/Windows_Server_2022

looks like codebase is different Windows Server 2022 is based on the "Iron" codebase.[5] Its updates are incompatible with the Windows 10 operating system, as the "Iron" codebase was not used for it.[5] Like its predecessor, Windows Server 2019, it requires x64 processors.

I think we can keep windows-2022 till it is working and remove it if that also starts failing because now we already have win-10/11 for e2e added as gh-action.

@cfergeau
Copy link
Contributor

cfergeau commented May 6, 2024

Fwiw, we used to have a similar workaround 1b6bf222090f

Do you suggest that we should use a hack keep the windows-2019 runner job?

I only mean that I don't find the argument "we need a workaround to keep the win2019 runners" very convincing when we already had a similar workaround in the past.

I think we can keep windows-2022 till it is working and remove it if that also starts failing because now we already have win-10/11 for e2e added as gh-action.

Fine with me, not even sure win2022 brings much as we have win10/win11 e2e?

Copy link
Contributor

@cfergeau cfergeau left a comment

Choose a reason for hiding this comment

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

ack from me with the confusing "win-2022 also have OS-10.0.x build" removed from the commit log.

@praveenkumar
Copy link
Member Author

ack from me with the confusing "win-2022 also have OS-10.0.x build" removed from the commit log.

removed it from the commit message.

Copy link
Contributor

@cfergeau cfergeau left a comment

Choose a reason for hiding this comment

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

I'd delay this after the next release though.

Copy link
Contributor

@cfergeau cfergeau left a comment

Choose a reason for hiding this comment

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

I'd delay this after the next release though.

Copy link

openshift-ci bot commented May 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfergeau

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

@praveenkumar
Copy link
Member Author

I'd delay this after the next release though.

@cfergeau because of RHEL-8.10 still not out?

/hold

@cfergeau
Copy link
Contributor

cfergeau commented May 6, 2024

I'd delay this after the next release though.

@cfergeau because of RHEL-8.10 still not out?

/hold

In a more general way, we don't want to discover during the release that "something" was not ready for go 1.21. But yes, I think we do our linux release builds on a rhel8, so this is one good reason for waiting with this change.

Copy link

openshift-ci bot commented May 7, 2024

New changes are detected. LGTM label has been removed.

@praveenkumar praveenkumar changed the title Some changes to update-version-go script to make it bit efficient and add the CI step to verify it Update to go-1.21 May 23, 2024
praveenkumar and others added 4 commits May 23, 2024 13:56
RHEL-9.4 and RHEL-8.10 is released and have golang-1.21 as part of go-toolset, same
with the ubi9/ubi8 go-toolset images. This PR do followingings
- Update github actions to go-1.21
- Use rhel-8-release-golang-1.21-openshift-4.16 image tag instead
  rhel-8-release-golang-1.20-openshift-4.15 because openshift-4.15
  doesn't have golang-1.21 tag.
It's been deprecated in go 1.21:
https://pkg.go.dev/crypto/elliptic#Marshal
> Deprecated: for ECDH, use the crypto/ecdh package. This function
> returns an encoding equivalent to that of PublicKey.Bytes in
> crypto/ecdh.

This fixes a `make lint` failure.
Looks like with `go-1.21` this job is failing because of outdate Mingw
version microsoft/go#1081 and there is hack to
make it work https://github.com/containerd/containerd/pull/9288/files.
Copy link

openshift-ci bot commented May 23, 2024

@praveenkumar: The following test 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/security 7f1fb1b link false /test security

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-sigs/prow repository. I understand the commands that are listed here.

@praveenkumar praveenkumar merged commit deb0649 into crc-org:main May 23, 2024
23 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants