Skip to content

Conversation

@AkihiroSuda
Copy link
Member

@AkihiroSuda AkihiroSuda added the area/ci e.g., CI failure label Feb 25, 2025
@AkihiroSuda AkihiroSuda added this to the v2.0.4 milestone Feb 25, 2025
Copy link
Member

@fahedouch fahedouch left a comment

Choose a reason for hiding this comment

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

🚀

@apostasie
Copy link
Contributor

New instance is likely much smaller than what we had (timeouting here).

Given the current state of the runners, suggesting we bump the timeout (#3931) until I figure out a way to reduce run time.

@fahedouch
Copy link
Member

New instance is likely much smaller than what we had (timeouting here).

Given the current state of the runners, suggesting we bump the timeout (#3931) until I figure out a way to reduce run time.

ubuntu-24.04-arm should perform better than ubuntu-24.04-amd64 which is successful in the last pipeline 🤔

@apostasie
Copy link
Contributor

New instance is likely much smaller than what we had (timeouting here).
Given the current state of the runners, suggesting we bump the timeout (#3931) until I figure out a way to reduce run time.

ubuntu-24.04-arm should perform better than ubuntu-24.04-amd64 which is successful in the last pipeline 🤔

ubuntu-24.04-arm had a significantly slower dependencies-prep step (+ 3 minutes - possibly because of invalidated github cache), which was enough to bring it over the total 30 minutes timeout.

I am refactoring the Dockerfile right now to deal with the new world order of 2025, where (amongst other things), github instances are smaller and where github cache sucks even more than in 2024 :p

@ktock ktock merged commit c12aaa3 into containerd:main Feb 26, 2025
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci e.g., CI failure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants