Project-1CE/system_update_engine - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2019-05-22	Skip an async callback function when the UpdateBootFlagsAction object is ↵	Tianjie Xu
	destroyed As the callback to MarkBootSuccessfulAsync, UpdateBootFlagsAction's member function CompleteUpdateBootFlags() can still be called even after the current UpdateBootFlagsAction object get destroyed by the action processor. We want to set a static flag in TerminateProcessing() and check its value before executing the callback function. An alternative way is to save and propagate the TaskId when scheduling the task in MarkBootSuccessfulAsync, and cancel the task in UpdateBootFlagsAction's TerminateProcessing(). Bug: 123720545 Test: No longer hit the CHECK after injecting StopProcessing. Change-Id: I98d2cc7b94d4059fb897b89932969b61936e8c2e (cherry picked from commit e1f55b0f39a109760ce6983d0b8f6f498ec90f52)
2018-10-12	Uprev libchrome to r576279 (1/multiple)	Jakub Pawlowski
	* StatisticsRecorder no longer need call to Initialize() * tracked_objects::Location -> base::Location * base::*ToString replaced with base::NumberToString Test: compilation Change-Id: I5f912bd15f7cb26df3edc1ad7f4479122ffb6d7a Merged-In: I5f912bd15f7cb26df3edc1ad7f4479122ffb6d7a (cherry picked from commit b09c78648893f5a8225fb1c5f9ac49946682fe31)
2018-07-25	update_engine: Pospone setgoodkernel after update check	Amin Hassani
	Currently, if an update is forced, we first run setgoodkernel and then continue with the update check. However, this delays the update check screen in the OOBE. This patch adds a new Action, UpdateBootFlagsAction which is configured to run AFTER an update check and response. However, now if the update check failed due for example the response was invalid, then setgoodkernel will not happen. But we already have a mechanism in SystemState where setgoodkernel is always called (currently) 45 seconds after the boot. So there would no worries. BUG=chromium:807976 TEST=unittests TEST=powerwashed the device, and the check for update passed faster on OOBE. Change-Id: I5845d7a4c1393aec568b6279dfbb7d3dfa31cdd8 Reviewed-on: https://chromium-review.googlesource.com/1011244 Commit-Ready: Amin Hassani <ahassani@chromium.org> Tested-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Sen Jiang <senj@chromium.org>