| 80e1541e2cee9c253a750dac42533a3749a5eeb9 |
|
24-Mar-2016 |
Julius Werner <jwerner@chromium.org> |
firmware_EventLog: Test for hardware watchdog event
This patch adds a check for the watchdog timeout event to the
firmware_EventLog test. Skipping x86 devices for now which don't seem to
report this event (at least on my old Falco).
Also change all the TestError in this test to TestFail which is actually
the correct exception to throw for cases where the board doesn't meet
expectations (as opposed to cases where the test logic itself ran into
an unexpected condition somehow).
BUG=None
TEST=Ran on Oak.
Change-Id: Ie00e471b5cad5048ca76a1bf13b5f4d4b9946696
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/334744
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
/external/autotest/server/site_tests/firmware_EventLog/firmware_EventLog.py
|
| 5e0ca61c64feb752512b1e66c2135de50c04bf66 |
|
03-Mar-2016 |
Duncan Laurie <dlaurie@chromium.org> |
firmware_EventLog: Disable suspend_to_idle for suspend/resume test
Skylake platforms have moved to using S0ix instead of S3 by default,
which means firmware is not involved in the process and no events
are logged. In order to continue to test the suspend/resume events
have the test disable suspend_to_idle before this test step and then
re-enable after.
BUG=chrome-os-partner:50758
BRANCH=glados
TEST=pass firmware_EventLog on chell with OS image 7890+
Change-Id: I01ab382731298072e299fb5588df4373b50918cb
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/330169
Reviewed-by: danny chan <dchan@chromium.org>
/external/autotest/server/site_tests/firmware_EventLog/firmware_EventLog.py
|
| 19bfb6ea468c34e1b44842033eb784c2ef3eed42 |
|
20-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Move wait_for_client and wait_for_client_offline to ModeSwitcher
These two methods are tightly related to ModeSwitcher. This change
helps it to be derived to different implementations.
BUG=chrome-os-partner:39744
TEST=Ran some of the effected FAFT tests.
Change-Id: Id9be1decec3ebc5a843a30b3070a2352546423eb
Reviewed-on: https://chromium-review.googlesource.com/294773
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_EventLog/firmware_EventLog.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_EventLog/firmware_EventLog.py
|
| da6c6ba556ebb2b810dd7450860609d6725afb1d |
|
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Support waiting DUT online after mode switching
A new argument wait_for_dut_up added to reboot_to_mode method. If
wait_for_dut_up=True, wait DUT online again. If wait_for_dut_up=False,
do the reboot and mode switching sequence only and may need more
operations to pass the firmware screen.
Also change most of the tests to use the default wait_for_dut_up=True
way, it helps porting these tests to different mode switching
implementations, like using dev and rec buttons.
BUG=chrome-os-partner:39744
TEST=Ran the affected test cases, like firmware_DevMode,
firmware_RecoveryButton, firmware_SelfSignedBoot, etc.
Change-Id: I723d43efe65e731d8a26b94822c094a9de8e8f11
Reviewed-on: https://chromium-review.googlesource.com/268859
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_EventLog/firmware_EventLog.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_EventLog/firmware_EventLog.py
|
| f2de4debd08a4825542fd4fd848ccd6b4fb000f8 |
|
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Implement the ModeSwitcher class
This is the first change of the ModeSwitcher refactoring. It
introduces a new class ModeSwitcher to do normal, dev, and rec
mode switching sequence. The triggering logic mostly keeps the
same or does a minor modification from the original one.
BUG=chrome-os-partner:39744
TEST=Ran firmware_DevMode and firmware_RecoveryButton on Jerry.
These two tests cover major changes on switching to normal, dev,
and rec modes.
Change-Id: I96b435c6df7a9f4c80aaab5d1fa4a062aa7699bf
Reviewed-on: https://chromium-review.googlesource.com/268794
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_EventLog/firmware_EventLog.py
|
| 52f642425bebb9e5eb572d3bab42069e3f95d379 |
|
21-Jan-2015 |
Duncan Laurie <dlaurie@chromium.org> |
firwmare_EventLog: Allow "ACPI Wake" from S5 in recovery mode
When using servod to enter recovery mode the system comes up from
a cold/hard reboot and logs an S5 wake event. The checks for the
recovery mode incorrect events needs to allow S5 wake events but
still check for S3 wake events.
BUG=chrome-os-partner:30832
TEST=pass firmware_EventLog on samus
Change-Id: Icc9fecd68d4aa9d1aecbf96b5b88351de4902366
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/242260
Reviewed-by: Julius Werner <jwerner@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_EventLog/firmware_EventLog.py
|
| 9ece2c6fb01d4c29d23a7238def15bdf656c885c |
|
12-Dec-2014 |
Julius Werner <jwerner@chromium.org> |
Add firmware_EventLog test to verify event log generation and timestamps
This patch adds a new faft_lv4 test to validate the functionality of the
firmware event log. It will boot the system in normal, developer and
recovery mode, verifying that the right events are logged for each. It
also tests a suspend/resume cycle, allowing either the ACPI events used
on x86 boards or the userspace Sleep/Wake events introduced with Spring
and Pit. (We can't check for 'FW Wake' because not all not-x86 boards
have a resume component in firmware.) The events are correlated to the
test section they were generated in by their timestamps, so this also
confirms that accurate timestamps are generated.
CQ-DEPEND=CL:238467
BUG=chrome-os-partner:34108
TEST=Tested on Falco (ToT), Blaze (ToT) and Pi (release). Pi failed in
the expected manner because U-Boot is missing RTC support (and all
timestamps are added as 2000-00-00). Blaze failed because its
timestamps' months are off by one... turns out the RTC driver code was
incorrectly copied from the 0-based-month-using kernel to our
1-based-month-using coreboot.
Change-Id: I2760080030468ed71dd0b7359ac69a269f6ab47a
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/238078
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_EventLog/firmware_EventLog.py
|