Pull the reboot START logging out of job.reboot; the reboot END logging is
queued up by methods external to job.reboot (i.e. kernel.boot) and so the
START logging should be run from there as well; otherwise it's not possible
to call job.reboot properly without having to first queue up your own END
logging. The default should just work.
Risk: Low
Visibility: Code changes only; should have the same user-visible behaviour.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2316 592f7852-d20e-0410-864c-8624ca9c26a4
diff --git a/client/bin/kernel.py b/client/bin/kernel.py
index 595b997..885fbf3 100755
--- a/client/bin/kernel.py
+++ b/client/bin/kernel.py
@@ -508,6 +508,7 @@
self.add_to_bootloader(args=args, tag=self.installed_as)
# Boot it.
+ self.job.start_reboot()
self.job.reboot(tag=self.installed_as)
@@ -712,6 +713,7 @@
self.add_to_bootloader(args=args, tag=self.installed_as)
# Boot it.
+ self.job.start_reboot()
self.job.reboot(tag=self.installed_as)