-
Notifications
You must be signed in to change notification settings - Fork 616
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 CI to test against go1.19 #3108
base: master
Are you sure you want to change the base?
Conversation
FWIW; I saw some failures locally when running some tests. No problems were found in Moby CI, so it could be just a badly written test, or it's a code-path that's not used in Moby. |
cf8bd74
to
06da8e6
Compare
Same failure in CI;
|
4f8f3a2
to
385b462
Compare
f6a06c4
to
bca837b
Compare
|
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Suggestion from Cory; try with |
Studying the debug output more closely, and the swarmkit source, I now see that won't do anything. |
https://go.dev/issue/58792 might be related |
That, at a glance, looks very plausible yes (great find!). |
To be clear, the behaviour change in Go is a bugfix, not a regression. The test is broken and always has been. Also, the cross-signed certs have the same serial number as the template cert. While not the cause of the test failures, it's not kosher either to have more than one cert with the same subject and serial. |
- Description for the changelog