-
Notifications
You must be signed in to change notification settings - Fork 596
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
Can CRIU use arm based runners from Actuated? #2402
Comments
You can see how runc enabled this: opencontainers/runc#4142 |
A friendly reminder that this issue had no activity for 30 days. |
Hi @adrianreber @kolyshkin how many jobs do you think you'd be generating? |
Looking at the history of the last 6 months there were around 50 pull requests. A pull request takes a couple of attempts before it is merged, but I would say an average of 6 CI runs each for 50 pull requests. A common test setup we have is to built and test CRIU once with GCC and once with LLVM. That would mean 50 pull requests * running around 6 times * 2 CI setups. So maybe something like 600 runs in 6 months on average. 100 per month. The free GitHub Actions runners need around 25 minutes for building and running all tests in the last few months. @alexellis Is that helpful? |
Let's get your details if that's OK? https://docs.google.com/forms/d/e/1FAIpQLScA12IGyVFrZtSAp2Oj24OdaSMloqARSwoxx3AZbQbs0wpGww/viewform?usp=send_form |
Done. |
Access is enabled and working, this issue can be closed. |
Hello @alexellis, you mentioned in a runc and CRI-O ticket that Actuated now has 6.x based kernels for their aarch64 runners.
Would it be possible for CRIU to also use those runners for CI testing?
The text was updated successfully, but these errors were encountered: