| 870bfee10e885a38bee5e742707ca74d137b72e5 |
|
21-Sep-2015 |
Ted Kuo <tedkuo@ami.com.tw> |
FAFT: Remove _updater_setup
Remove _updater_setup since it's useless.
BUG=chrome-os-partner:42943
TEST=run_pylint
BRANCH=None
Signed-off-by: Ted Kuo <tedkuo@ami.com.tw>
Change-Id: I193258a7e5b065d7722d7761499ce95ff99627a0
Reviewed-on: https://chromium-review.googlesource.com/300853
Commit-Ready: Ted Kuo <tedkuo@ami.com.tw>
Tested-by: Ted Kuo <tedkuo@ami.com.tw>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| ea76792bf9d37e60038fbdbe7be90fafcb66e2fe |
|
28-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Use relative paths to copy required scripts to DUT
The '~' doesn't work recently. Fix it by using the relative paths.
BUG=chrome-os-partner:43314
TEST=Ran the affected tests.
Change-Id: I26ff028694fb1d6355249c2d29ca9813494b06cc
Reviewed-on: https://chromium-review.googlesource.com/295943
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/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| 4777624b69b3b223a5d3c3abe86000783f6c0e96 |
|
06-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Use mode_aware_reboot instead of reboot_warm and reboot_cold
This change removes reboot_warm, reboot_cold, reboot_warm_trigger,
and reboot_cold_trigger from FAFT framework and uses the new
mode_award_reboot method which does the same job.
BUG=chrome-os-partner:16231
TEST=Ran some of the affected FAFT tests on Jerry.
Change-Id: I9f0d1fd3416c7e4a624a915507dfa9c97f16d3e0
Reviewed-on: https://chromium-review.googlesource.com/269764
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| 0cc9a4fe28f221cfc73bb35c30fa79338c4b43f1 |
|
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Refactor setup_mode and restore_mode
The change moves and splits the original logic on setup_dev_mode and
restore_dev_mode to FAFTCheckers and ModeSwitcher. It is also enhanced
to support setting up all firmware modes, including recovery. They are
now methods in ModeSwitcher as they are highly related to mode
switching.
BUG=chrome-os-partner:39744
TEST=Switched DUT to normal mode and ran firmware_DevMode. Then
switched DUT to dev mode and run firmware_DevMode. Checked DUT
restored to the original mode state.
Change-Id: I16314d18b785da59473df3ef5e02f7fe8f2693b0
Reviewed-on: https://chromium-review.googlesource.com/268858
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| dc079db592a4012d52725469d6b675e4db1c83dd |
|
21-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Converting firmware_UpdateKernelDataKeyVersion to use new FirmwareTest class.
The new FirmwareTest class does not require the traditional dict of objects
that FAFTSequence required.
1. Converted the test to use the new flat function call style.
2. Added it to the faft_bios suite.
BUG=chromium:371185
TEST=Manually ran this test at desk against peppy device.
Change-Id: I8b31293646fd452959294ec80907a475c59729dc
Reviewed-on: https://chromium-review.googlesource.com/200768
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| 1f115ae9ee3c043e9577e7ce9872dc99323fdcb3 |
|
07-Nov-2013 |
Yusuf Mohsinally <mohsinally@chromium.org> |
Correctly using initialize() rather than setup() for FAFT tests.
FAFT tests have been using setup() (which is run once at autotest init), when
it should have instead used initialize() for running code before each
test case is run.
BUG=chromium:267175
TEST=Ran tests manually against Pit device to ensure that these changes did not
introduce problems.
Change-Id: If0e76e12b9f40249154d7b95a1375b2787a56304
Reviewed-on: https://chromium-review.googlesource.com/176024
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| 73c28f3abd6ec8de4dc5a8e6afca1d5e83eb59c7 |
|
03-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Reorginazing FAFT (server side) files.
Initial reorganization step while moves FAFT (autotest/server)
files over to packages. Naming and other cleanup will be performed
in additional CLs.
BUG=None
TEST=built and ran faft tests at desk against Link
Change-Id: I83712620c0e6816ec08b9afdf8c227a800734ea6
Reviewed-on: https://gerrit.chromium.org/gerrit/64408
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| d4340315f76fcae9a5e9430d0446705f4f8fa7b7 |
|
17-Jul-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Rename the module faftsequence to faft_classes
For preparing the future refactoring that splitting FAFTSequence into
multiple meaningful small classes, changes the original module name
faftsequence to faft_classes.
BUG=chrome-os-partner:21118
TEST=Manual
Ran the affected test cases, firmware_FAFTSetup, on Spring and passed.
Change-Id: I662cfc8d37a54711d7c52ff5322ed28a9a759ffe
Reviewed-on: https://gerrit.chromium.org/gerrit/62642
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| 0acb90544464af1cfa0169a9fa956641f0b6be6f |
|
26-May-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Remove the sync and delay after setting the kernel boot priority
The sync and delay are not necessary because the cgpt command of changing
kernel boot priority already calls fsync at the end. Increasing the delay
increases the chance of failure.
BUG=chrome-os-partner:19727
TEST=Manal
Run FAFT CgptStress on Link with >50 iterations without failure.
Change-Id: I37536910f222bc4df45375f9c82fdc7d2a1f9e19
Reviewed-on: https://gerrit.chromium.org/gerrit/56712
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| d43aa9b4568e0b1283d6ff535b87446b14a6e3b9 |
|
16-Nov-2012 |
Chun-ting Chang <ctchang@chromium.org> |
Classify methods in FAFTClient
There are too many methods in FAFTClient, so this CL is to classify them into
several groups: ec, bios, kernel. Methods which can be put into one of the
target group should be renamed with format _[group name]_[method name].
For example, dump_firmware should be modified to bios_dump. To call methods in
FAFTClient, use [group name].[method name].
BUG=chromium-os:36429
TEST=run firmware update tests
Change-Id: I7ead01246121b454c0a9f29e10bd026a77925e4f
Reviewed-on: https://gerrit.chromium.org/gerrit/38186
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Chun-Ting Chang <ctchang@chromium.org>
Tested-by: Chun-Ting Chang <ctchang@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| cf924e9b95c75543202b791dd842cee9fe84e722 |
|
29-Oct-2012 |
Chun-ting Chang <ctchang@chromium.org> |
Repack firmware update methods to a updater module.
Use firmware update associated methods by _updater object in faft_client.
This object should start from setup the temp directory, and finally cleanup
the temp directory. That's because it distinguishes a new test by checking if
the temp directory exists.
BUG=chromium-os:36429
TEST=run firmware update tests
Change-Id: I94dddf1162d136317ec4ff99bfe3bb478bf9752f
Reviewed-on: https://gerrit.chromium.org/gerrit/38175
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Chun-Ting Chang <ctchang@chromium.org>
Tested-by: Chun-Ting Chang <ctchang@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| b09a04183cf7017eb4b30ad28f5f81f1204c36b3 |
|
06-Nov-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Fix lint warning and error
This includes removing unnecessary 'pass' and unused argumenets.
BUG=chrome-os-partner:35902
TEST=Check tests still work.
Change-Id: Ifb9ac8348e7e26e2ea1a10b9c7e509f817e117b9
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/37424
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| 47d42ba469b82b51e45f755240eacad404b6122d |
|
31-Oct-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Fix lint warning
This includes:
- String format arguments as logging function paramters
- Unused loop counter
- Long line
- Unused import
- Disable W0702 when we want to catch any exception
BUG=chromium-os:35902
TEST=Run faft suite and passed.
Change-Id: I8442fefc5d0687dfe18c3563b5befbff750ba3a7
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/36998
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| fc700b5d2aa218357936661918f36f0d1a778595 |
|
13-Sep-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Change the action tuple to support error_msg
We used the format of action tuple before, like (function, arg1, arg2, ...).
We want to specify the error_msg such that an user knows better why the test
is failed. So this CL changes the action tuple to (function, args, error_msg).
The args and error_msg are optional. The args is either a value or a tuple
if multiple arguments.
BUG=chromium-os:22598
TEST=run_remote_tests.sh --remote=$DUT control.faft_lv1
run_remote_tests.sh --remote=$DUT control.faft_lv2
run_remote_tests.sh --remote=$DUT -a "new_ec=foo" control.faft_lv3
When a test fails, it returns somethings like:
13:31:58 INFO | FAIL firmware_CorruptFwBodyB.dev firmware_Corrupt
FwBodyB.dev timestamp=1347600718 localtime=Sep 14 13:31:58 Not succe
ed: calling <bound method firmware_CorruptFwBodyB.crossystem_checker of <firmwar
e_CorruptFwBodyB.firmware_CorruptFwBodyB object at 0x2d1f490>> with args ({'trie
d_fwb': '1', 'mainfw_act': 'B'},) returning False
Change-Id: I5f016da443ccc8c067a4621e6bf881ef99bdd481
Reviewed-on: https://gerrit.chromium.org/gerrit/33290
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| c8f2ca0c0ef0d43cbcd70bf9f38627c12172956c |
|
14-Sep-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Use normal full power-off process for the tests which change cgpt value
In normal cases, we use the hardware warm reboot after each step. It caused
an issue that some tests change a cgpt value but the new value seems to be
cached in the block device, not fast enough to write the physical disk.
This CL changes the reboot action to use the normal full power-off process,
which presses the power-button. The system shutdown process should write all
cached data to the physical disk. It takes longer time to reboot but it acts
like more realistic user behavior.
BUG=chrome-os-partner:14055
TEST=Run firmware_CorruptKernelB passed on Snow.
Change-Id: Id5c1ada4b727cc48eb80f4b6820a795db05f424f
Reviewed-on: https://gerrit.chromium.org/gerrit/33268
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|
| cc88d11b36bd49bc763b65bba8b7443de2e45d01 |
|
23-Aug-2012 |
ctchang <ctchang@chromium.org> |
Autotest: firmware_UpdateKernelVersion and firmware_UpdateKernelDataKeyVersion
These two tests individually modify kernel version and kernel data key version.
On runtime, they modify kernel b directly, and reboot. Then, check the version,
and recovery.
BUG=chrome-os-partner:12442
TEST=run_remote_tests.sh --remote=$REMOTE_IP --board=$BOARD --servo
firmware_UpdateKernelVersion(or firmware_UpdateKernelDataKeyVersion)
Change-Id: Ic3ad3caed47ed6cdffc41d6df6f4696b74d350b7
Reviewed-on: https://gerrit.chromium.org/gerrit/31208
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Chun-Ting Chang <ctchang@chromium.org>
Tested-by: Chun-Ting Chang <ctchang@chromium.org>
/external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/firmware_UpdateKernelDataKeyVersion.py
|