-
Notifications
You must be signed in to change notification settings - Fork 99
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
Fix remove ring #135
Fix remove ring #135
Conversation
Night error issue #136 |
Signed-off-by: Xynnn007 <[email protected]>
The errors of Hi @jiangliu @arronwy I've changed previous CI tests for different combinations of features. Please take a look if it looks good to you. Hi @stevenhorsman @BbolroC This PR will help |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Xynnn007 , LGTM!
`sigstore-rs` has features `native-tls` and `rustls-tls`. The two features are leveraged to give two types of build: `kata-cc-rustls-tls` and `enclave-cc-rustls-tls`: they depend on purely rust implementation of crypto suites, including `ring` which can not be built on `s390x`. `kata-cc-native-tls` and `enclave-cc-native-tls`: they depend on `openssl` for crypto suites. They can be built on `s390x`. sync blocking is used because the current implementation of oci client is not `Send` between threads. Fixes: #134 Signed-off-by: Xynnn007 <[email protected]>
*-cc-* features will cover the tests of signature-cosign-*, encryption enclave-cc-* features will cover the tests of snapshot-unionfs Only four basic feature tests are left: - enclave-cc-rustls-tls: encalve-cc tests based on purely rust implementation - enclave-cc-native-tls: enclave-cc tests based on openssl - kata-cc-rustls-tls: kata-cc tests based on purely rust implementation - kata-cc-native-tls: kata-cc tests based on openssl Kata-cc tests are also combined with gRPC and ttrpc, while enclave-cc tests are based on native. Signed-off-by: Xynnn007 <[email protected]>
@Xynnn007 - just to double check - this mean we can remove the separate
If so I'll try removing it and enabling the co-sign tests for s390x (we might have to mutli-arch enable/create the s390x versions of those to get them passing, but it will be good to understand and work on that early in the release cycle. Thanks for the great work! |
Yes. To make it easy we can choose |
Fixes: #134