From 5b9c9ba1e036f6dc1e2b3310baccbd63ab8641f2 Mon Sep 17 00:00:00 2001 From: David Anderson Date: Thu, 11 Aug 2022 22:12:19 -0700 Subject: [PATCH 1/2] libsnapshot: Remove flaky image creation test. This test has always been flaky, and is not testing something super valuable: we know that image creation succeeds throughout the rest of the suite, so it's not very interesting to know that it can succeed in a low-space scenario. The inverse test is much more valuable, since we want the correct status code when creation fails due to low space. Bug: 240391002 Test: vts_libsnapshot_test Change-Id: I6235d11033d2f30efe530077b877863ba2574810 (cherry picked from commit 97e8a2f0e963cea957ffd135be4436de3b3afd6a) --- fs_mgr/libsnapshot/snapshot_test.cpp | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/fs_mgr/libsnapshot/snapshot_test.cpp b/fs_mgr/libsnapshot/snapshot_test.cpp index c145da718..e7ffb1600 100644 --- a/fs_mgr/libsnapshot/snapshot_test.cpp +++ b/fs_mgr/libsnapshot/snapshot_test.cpp @@ -2609,7 +2609,6 @@ class ImageManagerTest : public SnapshotTest, public WithParamInterfaceBackingImageExists(kImageName) || image_manager_->DeleteBackingImage(kImageName)); @@ -2618,19 +2617,6 @@ class ImageManagerTest : public SnapshotTest, public WithParamInterface userdata_; }; -TEST_P(ImageManagerTest, CreateImageEnoughAvailSpace) { - if (userdata_->available_space() == 0) { - GTEST_SKIP() << "/data is full (" << userdata_->available_space() - << " bytes available), skipping"; - } - ASSERT_TRUE(image_manager_->CreateBackingImage(kImageName, userdata_->available_space(), - IImageManager::CREATE_IMAGE_DEFAULT)) - << "Should be able to create image with size = " << userdata_->available_space() - << " bytes"; - ASSERT_TRUE(image_manager_->DeleteBackingImage(kImageName)) - << "Should be able to delete created image"; -} - TEST_P(ImageManagerTest, CreateImageNoSpace) { uint64_t to_allocate = userdata_->free_space() + userdata_->bsize(); auto res = image_manager_->CreateBackingImage(kImageName, to_allocate, From bfd3e3828491d5e97e5860c84cba716275e9cd8e Mon Sep 17 00:00:00 2001 From: biandonglei Date: Sat, 17 Sep 2022 14:43:50 +0800 Subject: [PATCH 2/2] Some device that platform base on android12 doesn't support A/B update, it looks virtual A/B is also not mandatory. so this test case should check ro.vendor.api_level first. test: run vts -m vts_ota_config_test -t VAB#Enabled issue: 245441425 Change-Id: I1795c931b28fd5fe28aa0f23717d4238fb352d37 --- fs_mgr/libsnapshot/vts_ota_config_test.cpp | 3 +++ 1 file changed, 3 insertions(+) mode change 100644 => 100755 fs_mgr/libsnapshot/vts_ota_config_test.cpp diff --git a/fs_mgr/libsnapshot/vts_ota_config_test.cpp b/fs_mgr/libsnapshot/vts_ota_config_test.cpp old mode 100644 new mode 100755 index 02bcc3438..d387eb32d --- a/fs_mgr/libsnapshot/vts_ota_config_test.cpp +++ b/fs_mgr/libsnapshot/vts_ota_config_test.cpp @@ -22,6 +22,9 @@ static int GetVsrLevel() { } TEST(VAB, Enabled) { + if (!android::base::GetBoolProperty("ro.build.ab_update", false) && (GetVsrLevel() < __ANDROID_API_T__)) { + GTEST_SKIP(); + } ASSERT_TRUE(android::base::GetBoolProperty("ro.virtual_ab.enabled", false)); if (GetVsrLevel() < __ANDROID_API_T__) { GTEST_SKIP();