PvmfwImgTest: Use actually invalid config data version
Since aosp/2714274, configuration data blobs of a version v1.x more
recent than the latest version known to pvmfw are being accepted to
provide forward compatibility with the system bootloader. As a result,
testInvalidConfigVersion_doesNotBoot is now failing because the version
it uses (v1.100) has become valid so that the pVM boots successfully.
Instead, use v2.0, denoting a breaking change in the format, which must
therefore be rejected by pvmfw (until we introduce said version).
Bug: 296207806
Bug: 297342022
Test: TH
Change-Id: I6725f7a4e081c598b8b5cfd78d561f3b0e6ce0f6
diff --git a/tests/hostside/java/com/android/microdroid/test/PvmfwImgTest.java b/tests/hostside/java/com/android/microdroid/test/PvmfwImgTest.java
index 30ad9e2..320b722 100644
--- a/tests/hostside/java/com/android/microdroid/test/PvmfwImgTest.java
+++ b/tests/hostside/java/com/android/microdroid/test/PvmfwImgTest.java
@@ -143,7 +143,7 @@
public void testInvalidConfigVersion_doesNotBoot() throws Exception {
// Disclaimer: Update versions when it becomes valid
Pvmfw pvmfw =
- new Pvmfw.Builder(mPvmfwBinFileOnHost, mBccFileOnHost).setVersion(1, 100).build();
+ new Pvmfw.Builder(mPvmfwBinFileOnHost, mBccFileOnHost).setVersion(2, 0).build();
pvmfw.serialize(mCustomPvmfwBinFileOnHost);
assertThrows(