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

[ci] update go version to 1.21 in cirrus ci #4198

Merged
merged 1 commit into from
Feb 8, 2024

Conversation

lifubang
Copy link
Member

@lifubang lifubang commented Feb 8, 2024

As go has released v1.22.0, so there is no 1.20.x in https://go.dev/dl/?mode=json anymore.
Let's update go version to 1.21.x in cirrus ci.

This will fix the error:

# Find out the latest minor release URL.
eval $(curl -fsSL "${PREFIX}?mode=json" | jq -r  --arg Ver "$GO_VERSION" '.[] | select(.version | startswith("go\($Ver)")) | .files[] | select(.os == "linux" and .arch == "amd64" and .kind == "archive") | "filename=\"" + .filename + "\""')
curl -fsSL "$PREFIX$filename" | tar Cxz /usr/local
gzip: stdin: not in gzip format
tar: Child died with signal 13
tar: Error is not recoverable: exiting now
curl: (23) Failed writing body (679 != 1401)

@lifubang
Copy link
Member Author

lifubang commented Feb 8, 2024

I let #4193 opening because there are some issues for runc with go 1.22.0.
Once #4192 merged, please rebase this PR to re-trigger the CI.

Signed-off-by: lfbzhm <lifubang@acmcoder.com>
@kolyshkin
Copy link
Contributor

Oh well, now vagrant up is not working in Cirrus CI. I spent an hour staring at the logs. Found out that:

  • all the packages are of the same version (compared with older logs when it worked)
  • CPU seems to be the same (and has vmx)
  • kvm and kvm_intel kernel modules are loaded
  • libvirtd is up and running, no errors in journalctl
  • No AVC denials in the kernel log (except for dnsmasq trying to run /bin/true but it seems to be a known issue, which should not break anything)

I am stuck here. @AkihiroSuda can you please take a look? Here is my changes to .cirrus.yml to add debug: kolyshkin@fa15bd2

@kolyshkin
Copy link
Contributor

Oh well, now vagrant up is not working in Cirrus CI. I spent an hour staring at the logs. Found out that:

  • all the packages are of the same version (compared with older logs when it worked)
  • CPU seems to be the same (and has vmx)
  • kvm and kvm_intel kernel modules are loaded
  • libvirtd is up and running, no errors in journalctl
  • No AVC denials in the kernel log (except for dnsmasq trying to run /bin/true but it seems to be a known issue, which should not break anything)

I am stuck here. @AkihiroSuda can you please take a look? Here is my changes to .cirrus.yml to add debug: kolyshkin@fa15bd2

opened #4199

@kolyshkin
Copy link
Contributor

We can still merge this one as it fixes the issue with cirrusci / centos tasks.

@kolyshkin kolyshkin merged commit 56cc1be into opencontainers:main Feb 8, 2024
44 of 45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants