| fd46140040e1cc0b7185e69be28ce37f0c353264 |
|
29-Jan-2016 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Increase the retry count to 4 on all FAFT tests
Experiement by setting the job retry count from 2 to 4, to see
if any improvement on the flaky issues.
BUG=None
TEST=None, trivial change.
Change-Id: I74da0dc8504ca3facad9476c05b287cf989bcee3
Reviewed-on: https://chromium-review.googlesource.com/324590
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_ECWriteProtect/control.dev
|
| fbf9c952fd8b384cc1a72b7fd2dda4650b1e150a |
|
14-Jan-2016 |
Aseda Aboagye <aaboagye@google.com> |
autotest: Add EC-3PO nightly FAFT suite.
Gearing for the 1st release of EC-3PO in servo, add a suite to be run in
the experimental FAFT EC group. This suite should be removed once the
results are satisfactory.
BUG=chrome-os-partner:46054
BRANCH=None
TEST=site_utils/suite_scheduler/suite_scheduler.py --sanity
Change-Id: Ibb7cf82aaf850ad8de8e0a45edc4970e6e76833d
Signed-off-by: Aseda Aboagye <aaboagye@google.com>
Reviewed-on: https://chromium-review.googlesource.com/321975
Commit-Ready: Aseda Aboagye <aaboagye@chromium.org>
Tested-by: Aseda Aboagye <aaboagye@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/control.dev
|
| fe25db701fa1dafdcaf71d5422f69d45342795a9 |
|
22-Sep-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Add retry to test in suites faft_ec and faft_bios
Command to add JOB_RETRIES = 2:
git grep -w faft_ec | grep SUITE | grep firmware | awk {'print $1'} | \
sed s/:SUITE//g | xargs -i sed -i -- \
's/TEST_TYPE = "server"/TEST_TYPE = "server"\nJOB_RETRIES = 2/g' {}
BUG=chromium:534742
TEST=None
CQ-DEPEND=CL:301387
Change-Id: I7964ce0ee5322036b4c3588c15a236475e58e5d2
Reviewed-on: https://chromium-review.googlesource.com/301347
Commit-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/control.dev
|
| 5e10d184f6f794137353b954a37f172f2f6284ea |
|
23-Jul-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Refine the test names of running under special modes
The tests running under special modes, like dev mode or ec wp'ed
mode, used the same names as running under normal mode. It makes
the test_that script confused to run multiple tests. Refine the
test name to make it clearer.
BUG=None
TEST=None, trivial tag changes.
Change-Id: I7b796ca64feb63d511b5314e603513bffe0caeaa
Reviewed-on: https://chromium-review.googlesource.com/287650
Trybot-Ready: Wai-Hong Tam <waihong@chromium.org>
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/server/site_tests/firmware_ECWriteProtect/control.dev
|
| aa7ec8c17b2c52168ec212b926de38de40f04e5c |
|
06-May-2015 |
Shuqian Zhao <shuqianz@chromium.org> |
[autotest] Seed ATTRIBUTES in all control files in autotest
The SUITE tag in the control files is being phased out and replaced by
ATTRIBUTES. During the transition period, both SUITE and ATTRIBUTES tags
will coexist, and a pre-upload hook will enforce that they agree with each
other and also ATTRIBUTES are in the attribute whitelist.
BUG=chromium:482749
TEST=Test with the pre-upload hook
Change-Id: I58288ff97c37af0b356115899b0d98e4052bc725
Reviewed-on: https://chromium-review.googlesource.com/269667
Reviewed-by: Shuqian Zhao <shuqianz@chromium.org>
Commit-Queue: Shuqian Zhao <shuqianz@chromium.org>
Trybot-Ready: Shuqian Zhao <shuqianz@chromium.org>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/control.dev
|
| 0ca40e28b664c76d62909b1a344738dfb6f7e936 |
|
28-Aug-2013 |
Fang Deng <fdeng@chromium.org> |
[autotest] Rename site_host.SiteHost to cros_host.CrosHost
Rename site_host.SiteHost to cros_host.CrosHost.
cros_host.CrosHost is the new chromeos specific host class.
The concept 'SiteHost' is deprecated as we are dealing with
multiple types of hosts (e.g. ServoHost).
The concept of a single'SiteHost' doesn't meet our needs any more.
All references are updated.
SerialHost is now subclassing RemoteHost and mixes in CrosHost
in hosts.factory.create_host().
BUG=chromium:273833
TEST=Trybot build passes; Repair/Verify pass;
Dummy suite passes;
Server side test platform_InstallTestImage
which is affected by this CL passes.
DEPLOY=scheduler
Change-Id: I5e59194996c67c6b5d7fdcaf40d594ea08de1af5
Reviewed-on: https://chromium-review.googlesource.com/167182
Tested-by: Fang Deng <fdeng@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/control.dev
|
| 54f4c58c6a92593314c0dff20e9419831f694af3 |
|
17-Jul-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Remove the legacy use_pyauto and use_faft arguments
These two arguements were introduced when ServoTest supported connecting
remote PyAuto and FAFT Client RPC servers. Now ServoTest only serves
FAFT Client, meaning that use_pyauto is always False and use_faft is always
True. So remove these arguments.
BUG=chrome-os-partner:21118;chromium-os:215491
TEST=Manual
Ran the affected test cases, firmware_FAFTSetup, on Spring and passed.
Change-Id: I5c740faddb97f81f052e720548bfce8a39b405e3
Reviewed-on: https://gerrit.chromium.org/gerrit/62641
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@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_ECWriteProtect/control.dev
|
| b6da6c375368af5032e31c56a3bc391bc46efb13 |
|
24-Jan-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Categorize FAFT tests into faft_normal, faft_dev, and faft_ec
To speed-up running FAFT, we should run faft_normal, faft_dev, and faft_ec
tests separately, saving time to switch mode. So all non-EC FAFT should be
categorized into these 3 groups. This CL add the tests which miss this field.
BUG=chromium-os:38141
TEST=None, trivial change
Change-Id: I9fa0335dbc53a874d1f08a16b92b20447d41d777
Reviewed-on: https://gerrit.chromium.org/gerrit/41915
Commit-Queue: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/control.dev
|
| f636752030e7cb5cec77657eb9182b3bff564606 |
|
23-Jan-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Change the TIME and TEST_CATEGORY fields of FAFT control files
The TIME field is how long the test runs. The definition:
SHORT < 15m, MEDIUM < 4 hours, LONG > 4 hour
This CL is to change them to fit this rule. And make the stress tests to
the proper category.
BUG=None
TEST=None, trivial change
Change-Id: I60bf03fb295a1907b55083a60fda1f0f76dfbc86
Reviewed-on: https://gerrit.chromium.org/gerrit/41793
Reviewed-by: Vic Yang <victoryang@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_ECWriteProtect/control.dev
|
| 84e06c129e841fc1f7ea8c1598295712d94a5877 |
|
16-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Revert "faft: Don't disable sysinfo, as local_dash uses sysinfo to get fw versions"
This reverts commit d6da7bf306f6ca5a64d530828ba9a77cb21f4cf9
The original fix is not a good idea since it rapidly consume disk space. It can be fixed in local_dash. Check more info in the bug.
BUG=chromium-os:36326
Change-Id: I0a0e8ca403e4c619f1352bc070a1c05ccf058d02
Reviewed-on: https://gerrit.chromium.org/gerrit/38171
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_ECWriteProtect/control.dev
|
| d6da7bf306f6ca5a64d530828ba9a77cb21f4cf9 |
|
13-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Don't disable sysinfo, as local_dash uses sysinfo to get fw versions
local_dash (generate_test_report) gets fw versions by parsing sysinfo dir.
However, FAFT tests disable sysinfo. local_dash was able to get fw versions
because they also run firmware_FAFTClient with sysinfo enabled.
A recent change makes FAFT tests no longer run firmware_FAFTClient:
https://gerrit.chromium.org/gerrit/37697
So local_dash failed to generate a correct json file then. This CL is to
enable sysinfo and makes local_dash works again.
BUG=chromium-os:36163
TEST=Run a FAFT test and call local_dash to update the json file.
Change-Id: I72fba6c31443bccd0c9c9eaca5ff017dafb9e68d
Reviewed-on: https://gerrit.chromium.org/gerrit/37881
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_ECWriteProtect/control.dev
|
| 964fba0ca6f0bbdf857b43d6d006190495b00a57 |
|
25-Oct-2012 |
J. Richard Barnette <jrbarnette@chromium.org> |
Change servo-related boilerplate in control files.
Control files for servo tests contained standard boilerplate
needed to help support running tests via run_remote_tests.sh.
The boilerplate posed a minor maintenance hazard, made more
serious by the sheer number of tests that had copied the
boilerplate code.
This change switches the boilerplate to something (hopefully) less
likely to need to change, before the size of the maintenance hazard
gets any bigger.
BUG=chromium-os:35685
TEST=platform_LongPressPower using a remote servod, plus a careful review
Change-Id: Id7da90ec82c7faf60dd6eecfdec5e0734fa8e2a5
Reviewed-on: https://gerrit.chromium.org/gerrit/36521
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Craig Harrison <craigdh@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/control.dev
|
| 9233ebbed0261d06ad380f3cd4e1e52defaf96bf |
|
28-Sep-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Support servod in a different host on FAFT control files
The servo_host and servo_port arguments are now handled in SiteHost class, not
the original ServoTest class. So all FAFT control files should be changed.
This change is created by the following script:
grep -lrsI "use_faft=True" * | grep control | xargs \
sed -i -e "s/AUTHOR =/from autotest_lib.server import utils\n\n&/" \
-e "s/def run_.*:/args_dict = utils.args_to_dict(args)\n"\
"servo_host = args_dict.get('servo_host', 'localhost')\n"\
"servo_port = args_dict.get('servo_port', None)\n\n&/" \
-e "s/ host = hosts.create_host(machine)/"\
" host = hosts.create_host(machine, servo_host=servo_host,\n"\
" servo_port=servo_port)/" \
-e "s/ client = hosts.create_host(machine)/"\
" client = hosts.create_host(machine, servo_host=servo_host,\n"\
" servo_port=servo_port)/"
BUG=chromium-os:34787
TEST=manaul
Run servod in the same host:
$ run_remote_tests.sh --remote $DUT $CONTROL
Run servod in a different host, $SERVO_HOST
$ run_remote_tests.sh --remote $DUT --args "servo_host=$SERVO_HOST" $CONTROL
Some tests may fail since FAFT is not supported servod on a different host yet.
Change-Id: I879bb786999c585c81ef532a84dfa2df7fbf4854
Reviewed-on: https://gerrit.chromium.org/gerrit/34277
Reviewed-by: Mike Truty <truty@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_ECWriteProtect/control.dev
|
| 38d4885a9bc1ecbc1dd4d2399c55ff8e9bb2949e |
|
28-Aug-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Add a new test of EC write protect under software sync
This test starts with RO normal mode and enables EC write protect. Software sync
supposed to write protect the entire EC flash, so we expect the following
write protect flags:
- wp_gpio_asserted
- ro_at_boot
- ro_now
- all_now
These flags are checked under following situations:
- Cold reset. RO normal.
- Cold reset. Two stop.
- Cold reset by ectool. Two stop.
At the end of the test, write protect is deactivated and firmware is restored to
RO normal mode.
Signed-off-by: Vic Yang <victoryang@chromium.org>
BUG=chrome-os-partner:13229
TEST=Test passed on snow.
Change-Id: I821f8e6fe58702d94a09d8eb685e73fb17dfac29
Reviewed-on: https://gerrit.chromium.org/gerrit/31552
Commit-Ready: Vic Yang <victoryang@chromium.org>
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/control.dev
|