History log of /system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e6e4bb929acd73e57b68a30d1e3a33d76607aec3 05-Apr-2016 Sen Jiang <senj@google.com> Remove BootControlInterface from FilesystemVerifierAction.

update_engine now only runs FilesystemVerifierAction after DownloadAction,
the partition paths are already set in InstallPlan, so we no longer need
BootControlInterface to get partition paths in FilesystemVerifierAction.

Test: ./update_engine_unittests
Test: applied an update in edison
Bug: 26972259

Change-Id: I9d439688a21e4e42be88a4c5accf731ce64d2d6f
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
fef85fd9ece49941db274559a938fe8b2c5157bf 25-Mar-2016 Sen Jiang <senj@google.com> Remove ComputeSourceHash mode in FileSystemVerification action.

This mode was used to calculate the source partition hash before download
the payload, and we will verify it against the hash in the payload.
Now that we are using per-operation source hash, this mode is no longer
needed.

Test: ./update_engine_unittests
Test: cros_workon_make update_engine --test
Bug: 26972259

Change-Id: Ie30a38cfd9f94e4efe02dfc8664e6785018261f6
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
bf341e33b3b6cc55139a84a4934bbf649e825581 16-Mar-2016 Sen Jiang <senj@google.com> Clean up dead code in FilesystemVerifierAction.

Now that we switched to minor version 3, those code is dead.

The disabled unittest is using CreateExtImageAtPath which I'm about to
remove, so I'm removing this code now.

Test: mma
Bug: 26972259

Change-Id: Ic6a9b9e87e5e2aa09011cf005a4dee78391c6901
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
cbc2274c4160805bf726df872390112654816ca7 05-Mar-2016 Alex Deymo <deymo@google.com> Rework postinstall unittests to pass on Android.

Postinstall unittests were creating and mounting an image on each test
run. This patch adds several test scripts to one of the pre-generated
images and uses that image during postinstall testing instead.

To workaround problems with mount/umount of loop devices on Android,
this patch rewrites the `losetup` logic to make the appropriate
syscalls and create the loop device with mknod if it doesn't exists.

The tests require some extra SELinux policies to run in enforcing mode.

Bug: 26955860
TEST=Ran all Postinstall unittests.

Change-Id: I47a56b80b97596bc65ffe30cbc8118f05faff0ae
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
80f70ff45f8ea9a679c0c3ed0dc143dd2fe2b63e 11-Feb-2016 Alex Deymo <deymo@google.com> Build unittests in Brillo.

Many unittests do not pass for simple reasons that will be addressed
later. This CL includes all the changes to make the unittests build.
In particular, the generated DBus mocks, required to build several
unittests are now included here.

The dbus-constants.h files were moved to the system_api repo, so they
can be removed from here.

The unittest build is only enabled for Brillo targets, since non-Brillo
targets don't even build DBus.

Bug: 26955860
TEST=`mmma` on edison-eng (and aosp_arm-eng).

Change-Id: Ib38241f0a6eb99b1d60d72db6bcfd125d38e3fad
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
64d9878470aa7b388e971862181daf6260851602 06-Feb-2016 Alex Deymo <deymo@google.com> Replace is_full_update boolean with a payload_state enum.

The "is_full_update" flag in the InstallPlan is required to decide
whether we should run a FilesystemVerification step before start
downloading the payload (for delta payloads) or not (for full payloads).
This step is done before start downloading the payload and not after
downloading the metadata to avoid long delays in the connection which
would then drop and require a retry.

Since the not so recent inclusion of the source_data_hash field in the
delta operations, the source data is verified on each operation, so the
install plan field and the pre-download FilesystemVerification is not
needed anymore.

To help deprecate this process, which is not included in the non-Brillo
version, this patch changes the is_full_update field to a payload_state
enum with a third "unknown" state that will be changed to delta or full
once the payload metadata is parsed.

Bug: 25631949
TEST=unittests updated.
TEST=Pushed a delta update to edison-eng and a non-Brillo target.

Change-Id: I17d8bf58990d8465bb8487adc66601f1c1dfca6d
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
f9874815ce2fc82b76930e8cfc19a0811231cff9 09-Dec-2015 Sen Jiang <senj@google.com> Fix unittest in FilesystemVerifierActionTest.

Bug: 23182225
TEST=cros_workon_make update_engine --test

Change-Id: I9e440fa4adc79e8a0b6426b9b7aefd0d4209699a
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
1ad42adc806890b3a42bb729435a5cee83ef4e33 18-Nov-2015 Sen Jiang <senj@google.com> Optional source filesystem verification in minor version 3.

In minor version 3, we use per-operation source hash to verify the source
instead of whole filesystem hash, but if target partition doesn't match,
we still need to check the source partition to see if it is the cause.

Bug: 23182225
TEST=Applied a minor version 3 delta payload.
TEST=cros_workon_make update_engine --test

Change-Id: I1f32c292d2938540b63f086cf4988d64620702a5
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc
39910dcd1d68987ccee7c3031dc269233a8490bb 10-Nov-2015 Alex Deymo <deymo@google.com> Split payload application code into a subdirectory.

This patch splits from the main libupdate_engine code the part that
is strictly used to download and apply a payload into a new static
library, moving the code to subdirectories. The new library is divided
in two subdirectories: common/ and payload_consumer/, and should not
depend on other update_engine files outside those two subdirectories.
The main difference between those two is that the common/ tools are more
generic and not tied to the payload consumer process, but otherwise they
are both compiled together.

There are still dependencies from the new libpayload_consumer library
into the main directory files and DBus generated files. Those will be
addressed in follow up CLs.

Bug: 25197634
Test: FEATURES=test emerge-link update_engine; `mm` on Brillo.

Change-Id: Id8d0204ea573627e6e26ca9ea17b9592ca95bc23
/system/update_engine/payload_consumer/filesystem_verifier_action_unittest.cc