| d2eaa3f3af3f86aa7df0aed3726a0bff8ca526a2 |
|
02-Feb-2017 |
Wai-Hong Tam <waihong@google.com> |
FAFT: Fix firmware_TPMNotCorruptedDevMode by explicitly stopping tcsd/trunksd
tcsd/trunksd is no longer stopped when running a FAFT test. Explicitly call
APIs to stop/restart tcsd/trunksd.
BUG=chrome-os-partner:62150
TEST=Ran firmware_TPMNotCorruptedDevMode and passed the modified code.
Change-Id: I7de502820f741ed52c5230ac53a7c28fa86e635f
Reviewed-on: https://chromium-review.googlesource.com/436245
Commit-Ready: Wai-Hong Tam <waihong@google.com>
Tested-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Andrey Pronin <apronin@chromium.org>
/external/autotest/client/cros/faft/utils/tpm_handler.py
|
| 73d6adec5d387c330b85c4fd7e0473c84f651435 |
|
02-Feb-2017 |
Wai-Hong Tam <waihong@google.com> |
FAFT: Fix firmware_TPMKernelVersion by calling APIs to get kernel versions
tcsd/trunksd is no longer stopped when running a FAFT test. Fix the test
firmware_TPMKernelVersion by calling the related APIs which will stopped
tcsd/trunksd during reading the TPM NVRAM data.
BUG=chrome-os-partner:62150
TEST=Ran firmware_TPMKernelVersion and passed the modified code.
Change-Id: If55fa20c9709fa7e881e615ab04a49f6025820f2
Reviewed-on: https://chromium-review.googlesource.com/436244
Commit-Ready: Wai-Hong Tam <waihong@google.com>
Tested-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Andrey Pronin <apronin@chromium.org>
/external/autotest/client/cros/faft/utils/tpm_handler.py
|
| 48d92dcbae5b30b14bb7af84652af7a8b0eb8612 |
|
02-Feb-2017 |
Wai-Hong Tam <waihong@google.com> |
FAFT: Initialize the TPM handler only on TPM related methods
Initializing the TPM handler stops tcsd/trunksd and affects other
systems which depend on them. Moving the initializing step to TPM
related methods by reusing the LazyInitHandlerProxy class.
Also restarted tcsd/trunksd when done.
FAFT running on Android system will not run the TPM related tests.
So don't care about the Android system.
CQ-DEPEND=CL:436245
BUG=chrome-os-partner:62150
TEST=Ran a FAFT test and called the TPM related methods manually.
Change-Id: Ifcf0ee858281a7d561ff39a28061832fb22d1217
Reviewed-on: https://chromium-review.googlesource.com/435888
Commit-Ready: Wai-Hong Tam <waihong@google.com>
Tested-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Andrey Pronin <apronin@chromium.org>
/external/autotest/client/cros/faft/utils/tpm_handler.py
|
| 3a1d509b50ad4bbc5b7ffc1d964e45d7c98944f5 |
|
13-Jul-2016 |
Andrey Pronin <apronin@google.com> |
autotest: make sure neither trunksd nor tcsd runs for faft
For TPM2.0 trunksd is run instead of tcsd. So, make sure it is
stopped before using tpmc in FAFT and re-started afterwards.
Before the change rpc_server.py failed to start for tpm2 because
it tried to stop tcsd, which is not present and not known to
initctl if tpm2 is enabled.
BUG=chrome-os-partner:55210
TEST=Verify that rpc_server.py starts on kevin. verify that
'test_that --board=kevin $IP firmware_FAFTSetup' stops
trunksd before running and restarts during cleanup on
kevin.
Change-Id: I3f9f64fb8250838055e43153899ecded36f1ea56
Reviewed-on: https://chromium-review.googlesource.com/361392
Commit-Ready: Andrey Pronin <apronin@chromium.org>
Tested-by: Andrey Pronin <apronin@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
/external/autotest/client/cros/faft/utils/tpm_handler.py
|
| ba5e3e52352ba60c43212f17c1d133006ef31ebd |
|
31-Jul-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Change naming from "Chrome OS" to "OS"
Change the naming to prepare to run FAFT on other OSes.
BUG=chromium:516398
TEST=Ran a FAFT test to verify it not broken.
Change-Id: Iaa36274c648d2272ab0e0b8c369f8a89c5e6ee46
Reviewed-on: https://chromium-review.googlesource.com/290329
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
/external/autotest/client/cros/faft/utils/tpm_handler.py
|
| 9999730bc117c6a6363b616d3da5dbf0eb6b4d50 |
|
15-Jul-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Remove unused methods from FAFT client libraries
Some methods are not used by others. Remove them.
BUG=chromium:516398
TEST=Manual check the methods not used by others.
TEST=Ran the faft_lv1 test on Jerry.
Change-Id: Ic190bddf2408fdf20b7e1089d9988e74ede5eff5
Reviewed-on: https://chromium-review.googlesource.com/285856
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
Commit-Queue: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/client/cros/faft/utils/tpm_handler.py
|
| cd108dabef292c796ddd34f395ac653b61d931fc |
|
12-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Reorganizing FAFT client side code.
Created faft packages. Moved old saft modules into faft/utils. This is the
initial reorg step, and file/object names will be cleaned up in subsequent CLs.
Added a common.py which is necessary for setting up the autotest package
namespace.
BUG=None
TEST=Manually ran firmware_FAFTSetup at desk
Change-Id: I631b4457ad47cc15bfb9e3d915d75e648cb3d8f9
Reviewed-on: https://gerrit.chromium.org/gerrit/65614
Reviewed-by: Dennis Jeffrey <dennisjeffrey@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/client/cros/faft/utils/tpm_handler.py
|