-
Notifications
You must be signed in to change notification settings - Fork 34
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
Mark the s390x CI as non-required #470
Comments
Thanks for creating this issue @fidencio |
It turns out that the failure is resolved if the backport kata-containers/tests#4633 is merged (onto |
This will be valid until the jenkins slave is migrated to IBM cloud. |
The intergaration with IBM cloud has been finished. It has been showing that the CI jos for s390x gets stable since then. Even the running time becomes faster from 1h15m to 40m after kata-containers/tests#4919 and kata-containers/tests#4926 (see the results: http://jenkins.katacontainers.io/label/s390x-ubuntu-2004/). @fidencio could you include the jobs again as required and close this issue? |
I have updated the relevant CI jobs for s390x at http://jenkins.katacontainers.io/view/PR%20Triggered/ |
Currently the s390x CI has been re-enabled but it's still not 100% stable.
Let's mark this as non-required till @BbolroC sorts out the situation.
The text was updated successfully, but these errors were encountered: