Skip to content

Conversation

@kolyshkin
Copy link
Contributor

@kolyshkin kolyshkin commented Jul 26, 2024

As of #4290, we are already prepared, so the only things left to do are:

  • drop Go 1.21;
  • add Go 1.23;
  • for a few jobs that were using Go 1.21, switch to 1.22;

Also, bump go to 1.22 in go.mod.

🔔 For CI, see #4375.

@kolyshkin kolyshkin changed the title ci/gha: add go 1.23-rc1 ci/gha: add go 1.23-rc2 Jul 26, 2024
@kolyshkin kolyshkin force-pushed the go123 branch 2 times, most recently from 6fd183b to 649ec2c Compare July 26, 2024 07:02
@kolyshkin kolyshkin force-pushed the go123 branch 2 times, most recently from 58fe7d4 to a178aad Compare August 13, 2024 22:13
@kolyshkin kolyshkin changed the title ci/gha: add go 1.23-rc2 Add Go 1.23, drop 1.21 Aug 13, 2024
@kolyshkin kolyshkin marked this pull request as ready for review August 14, 2024 01:36
@kolyshkin kolyshkin added area/ci backport/1.1-done A PR in main branch which has been backported to release-1.1 labels Aug 14, 2024
@kolyshkin
Copy link
Contributor Author

1.1 backport: #4372

@kolyshkin
Copy link
Contributor Author

We need this one to fix cirrus-ci failing as it can't download Go 1.21. PTAL @opencontainers/runc-maintainers

module github.com/opencontainers/runc

go 1.21
go 1.22
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we keep this 1.22.4, since 1.22.0-3 has known issue with runc?

Copy link
Member

Choose a reason for hiding this comment

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

We want to test with the latest 1.22, not just 1.22.4. That will just test 1.22.4, right?

Sure, we don't want to test with earlier than 1.22.4, but IIUC there is no way to express that and no CI is using failing due to that (all are using older already). IMHO we should keep 1.22 to test the latest releases too.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right, alas there's no way to say "we want 1.22 >= 1.22.4" (I tried hard to find it but failed).

Copy link
Member

@rata rata left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

- drop Go 1.21;
- add Go 1.23;
- for a few jobs that were using Go 1.21, switch to 1.22;

Also, bump go to 1.22 in go.mod.

Signed-off-by: Kir Kolyshkin <[email protected]>
The warnings fixed were:

libcontainer/configs/config_test.go:205:12: printf: non-constant format string in call to (*testing.common).Errorf (govet)
		t.Errorf(fmt.Sprintf("Expected error to not occur but it was %+v", err))
		         ^
libcontainer/cgroups/fs/blkio_test.go:481:13: printf: non-constant format string in call to (*testing.common).Errorf (govet)
			t.Errorf(fmt.Sprintf("test case '%s' failed unexpectedly: %s", testCase.desc, err))
			         ^
libcontainer/cgroups/fs/blkio_test.go:595:13: printf: non-constant format string in call to (*testing.common).Errorf (govet)
			t.Errorf(fmt.Sprintf("test case '%s' failed unexpectedly: %s", testCase.desc, err))
			         ^

Signed-off-by: Kir Kolyshkin <[email protected]>
@kolyshkin
Copy link
Contributor Author

@AkihiroSuda PTAL (helps to unblock CI)

@lifubang lifubang merged commit 0377d50 into opencontainers:main Aug 15, 2024
@lifubang lifubang mentioned this pull request Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci backport/1.1-done A PR in main branch which has been backported to release-1.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants