Test Azure predictions #39
Conversation
|
@travier Tests are going to fail for 2 reasons. 1 is expected, efivars for azure aren't still merged in trusted-execution-clusters/reference-values#4. The other one is kind of unexpected for me. I get a prediction mismatch in the PCR4 part relative to vmlinuz. The VM I booted in azure is a So rather than a prediction issue, seems to be that the kernel version of the azure vm is different. Is this expected? |
All test fixtures were based on 42.20250705.3.0 which can be garbage collected. Stick to 42.20250929.3.0 in tests, which should not. Signed-off-by: Beñat Gartzia Arruabarrena <[email protected]>
It's already checked on the all-pcrs test implicitly. However, this way all tests follow the same structure, and test-vmlinuz is not a different one that just prints the output to stdout. Signed-off-by: Beñat Gartzia Arruabarrena <[email protected]>
bgartzi
force-pushed
the
azure-predictions
branch
2 times, most recently
from
7aa4326 to
f91b713
Compare
Adds test-fixtures for azure, and makes sure that tests for that platform are run in github ci. Adds the host-platform matrix variable to the tests job. For now, we will only test the azure platform with the fedora coreos 42 image as that's the only data we've gathered for now. It also excludes secureboot-disabled tests for the azure platform, as we haven't measured that case for now either. Signed-off-by: Beñat Gartzia Arruabarrena <[email protected]>
bgartzi
force-pushed
the
azure-predictions
branch
from
f91b713 to
cb6aba0
Compare
|
Rebased the branch onto the branch with #49 so tests, including those related to azure data, stick to fedora-42.20250929.3.0. Fixed some test-fixtures after fighting the big mess of json files and results I had in local. |
1 participant
This patch is built upon the patch sent to #38merged.It also depends on trusted-execution-clusters/reference-values#4 as it is adding the needed reference values for azure testing.
Edit: Now it also depends on #49