-
Notifications
You must be signed in to change notification settings - Fork 91
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
AS: tdx-quote verification unit test fails #399
Comments
I am diving into this. |
Well. This quote is generated on Alibaba cloud. GHA should connect to the PCCS of aliyun |
ok, this is what I assumed. Is there a way to store the response of PCCS as a fixture and make the unit tests use that (after refactoring the verification a bit to be able to use use output of |
I have requested a DCAP feature to be able to configure the PC(C)S settings more easily. With that, the test case can create a config file with the necessary |
@mkulke Yes. I thought I walked a big circle and finally got you at the beginning. Let me try to fix this in both ways -- I prefer to try changing pccs address first |
The example quotes need to configure a proper PCCS provided by Aliyun. Close confidential-containers#399 Signed-off-by: Xynnn007 <[email protected]>
The example quotes need to configure a proper PCCS provided by Aliyun. Close confidential-containers#399 Signed-off-by: Xynnn007 <[email protected]>
The example quotes need to configure a proper PCCS provided by Aliyun. Close confidential-containers#399 Signed-off-by: Xynnn007 <[email protected]>
The example quotes need to configure a proper PCCS provided by Aliyun. Close confidential-containers#399 Signed-off-by: Xynnn007 <[email protected]>
The example quotes need to configure a proper PCCS provided by Aliyun. Close confidential-containers#399 Signed-off-by: Xynnn007 <[email protected]>
there is a tdx quote verification unit test that fails atm. the test is disabled by default, most likely because you need a PCCS configured on the test system.
We should either remove that test or maybe consider rewriting the logic slightly so that we can store all external dependencies as fixtures for the unit test and cover real verification in an e2e test
The text was updated successfully, but these errors were encountered: