| dcff84266ccf29d474e902b597225a1e07cb765d |
|
15-Feb-2017 |
Tyler Reid <twreid@google.com> |
Adding tests for the recovery cache scenarios
BUG=b:35582651
TEST=Ran local against electro and kevin
Change-Id: Icb11caf9ad8188167a80037dbc28d8d21c23739d
Reviewed-on: https://chromium-review.googlesource.com/446576
Commit-Ready: Tyler Reid <twreid@google.com>
Tested-by: Tyler Reid <twreid@google.com>
Reviewed-by: Wai-Hong Tam <waihong@google.com>
/external/autotest/client/cros/faft/utils/saft_flashrom_util.py
|
| 6dd5843d5526bd472d61bc4a3dd38d1a8e5fe24b |
|
07-Dec-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: update SoftwareSync test to work with Android
In Android, SoftwareSync does not wait for device
to boot up after flashing the EC (which caused EC
to reboot), which will cause next adb call to fail,
ultimately failing the test. Added code to
accomodate this.
BUG=chrome-os-partner:48038
TEST=Ran SoftwareSync test on Smaug and Gnawty
Change-Id: Idbc9a8897bd8d4eee2709af07885e1fbf646c19b
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/316512
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/client/cros/faft/utils/saft_flashrom_util.py
|
| 38aa548ceb0f1fdb081deb9389b4c8e99aee485b |
|
31-Jul-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Wrap the shell command interface
This change wraps the shell command interface and uses it to
access DUT instead of call the Python library directly.
It helps easily to switch to other shells, like adb-shell.
BUG=chromium:516398
TEST=Ran FAFT suites to verify still working on Jerry.
Change-Id: If345dc669ee5bd8ce858cbce1e6a8978d90f18c2
Reviewed-on: https://chromium-review.googlesource.com/290350
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/saft_flashrom_util.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/saft_flashrom_util.py
|
| 22331b87b470527c17309695a07560d67cb9ddd1 |
|
31-Jul-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Pass the ChromeOSInterface object to flashrom_util
This change fixes a minor issue that the flashrom_util always
instantiated a new ChromeOSInterface object.
BUG=chromium:516398
TEST=Ran a firmware corruption test to exercise the flashrom_util.
Change-Id: I9e29b4fb5cde4b670e27be78ec36655725c18b8b
Reviewed-on: https://chromium-review.googlesource.com/290328
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/client/cros/faft/utils/saft_flashrom_util.py
|
| 6dc580a3b2ef48db27509a023fdfd64334aa946e |
|
08-Aug-2015 |
danny chan <dchan@chromium.org> |
Revert "FAFT: Reorganize the logging code"
This reverts commit 6db59cbabdc0e9b0ad823af319b4e40718a26c0f.
Change-Id: I5b4047f0c546a45f7e55ddfeae8dcb93496f5410
Reviewed-on: https://chromium-review.googlesource.com/291803
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/client/cros/faft/utils/saft_flashrom_util.py
|
| 6db59cbabdc0e9b0ad823af319b4e40718a26c0f |
|
21-Jul-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Reorganize the logging code
Use Python logging module to log the messages of FAFT client.
It flushes to disk per every output. It works the same as the
existing logging method of Chrome OS interface of FAFT.
BUG=chromium:516398
TEST=Ran a FAFT test and checked faft_client.log in the result dir.
Change-Id: I930a505e2a8f8f26488e30f5d8e5db29adb6b330
Reviewed-on: https://chromium-review.googlesource.com/290325
Reviewed-by: danny chan <dchan@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/client/cros/faft/utils/saft_flashrom_util.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/saft_flashrom_util.py
|
| 64161b4d52c8d313ade6427cd290b90ff1e26581 |
|
17-Dec-2014 |
David Hendricks <dhendrix@chromium.org> |
saft: Don't invoke mosys with -f
The -f flag forces mosys to ignore the global IPC lock and sanity
checking which can be really bad if stuff like flashrom is running
at the same time.
If -f is needed due to flashrom (or something) holding the lock, then
that may indicate another issue and should be addressed.
BUG=chrome-os-partner:34430
BRANCH=none
TEST=none
Change-Id: I860add89c884e238c960f706ee2ae05fb0282805
Reviewed-on: https://chromium-review.googlesource.com/236366
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
/external/autotest/client/cros/faft/utils/saft_flashrom_util.py
|
| 37bcc951d328d064255426a10ec6fd855c0eaeb4 |
|
03-Nov-2014 |
David Hendricks <dhendrix@chromium.org> |
autotest: Update flashrom syntax for "-p" option
This does a simple find/replace of instances where the old flashrom
"-p" syntax is used to specify the target. The new syntax is more
intuitive and more reliable since it removes any ambiguity about
what device is actually being targeted, since some targets such as
the EC can be on different busses on different platforms.
Old syntax:
Host/BIOS ROM: -p internal:bus=spi
EC: -p internal:bus=lpc
New syntax:
Host/BIOS ROM -p host
EC: -p ec
BUG=chrome-os-partner:33452
BRANCH=none
TEST=needs testing
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Change-Id: I5753a2f7402928dafbdaa31f5eec3f49612e1648
Reviewed-on: https://chromium-review.googlesource.com/226951
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/client/cros/faft/utils/saft_flashrom_util.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/saft_flashrom_util.py
|