| f45b3c753cfcc611287daadac0ee16575f3c990c |
|
26-Apr-2017 |
Aseda Aboagye <aaboagye@google.com> |
cros_firmware: Support the new "BIOS (RW)" field.
chromeos-firmwareupdate was recently changed to add some "RW" fields.
However, those fields now refer to the RO version of the firmware and
the "(RW)" fields refer to (as the name implies) the RW verison of the
firmware.
This commit changes the method of retrieving the RW firmware version to
check first for the "BIOS (RW) version" field and then fallback to the
previous method of just "BIOS version" if the field is not found.
BUG=chromium:714786
TEST=Take `chromeos-firmwareupdate -V` output from a caroline image and
a snappy image. Exercise the code and verify that it's able to extract
the correct BIOS firmware versions.
Change-Id: I653ba9f7ed50d287cc29c2dcce7ce599f60c01d6
Signed-off-by: Aseda Aboagye <aaboagye@google.com>
Reviewed-on: https://chromium-review.googlesource.com/487868
Commit-Ready: Aseda Aboagye <aaboagye@chromium.org>
Tested-by: Aseda Aboagye <aaboagye@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
/external/autotest/server/hosts/cros_firmware.py
|
| b6cea61e59b40819af04fbf9ced7dba75785d43e |
|
10-Feb-2017 |
Prathmesh Prabhu <pprabhu@chromium.org> |
Replaces usage of afe_utils.get_labels with HostInfo properties
BUG=chromium:678430
TEST=None
Change-Id: I3502e1d6baddd9f598634077854030005ceef290
Reviewed-on: https://chromium-review.googlesource.com/440563
Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/server/hosts/cros_firmware.py
|
| 075fc92c8af5eeb07ea5b9fa8ea253412ef71860 |
|
13-Feb-2017 |
Prathmesh Prabhu <pprabhu@chromium.org> |
[autotest] Drop uses of CrosHost._get_board_from_afe
BUG=chromium:678430
TEST=unittests
Change-Id: I1df262a0f600a791c0c35326b1b459cd931eded3
Reviewed-on: https://chromium-review.googlesource.com/439890
Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
/external/autotest/server/hosts/cros_firmware.py
|
| 1b489932343527b85fb391527cc59231ebad092c |
|
14-Feb-2017 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Check the results of firmware update.
In the standard firmware update verifier, after running
chromeos-firmwareupdate, check that the new firmware running on
the DUT matches the firmware we tried to install.
BUG=chromium:692149
TEST=test a successful repair run
Change-Id: I642b0e08e75fc6e0ba29d323ff36c64f295cf8cd
Reviewed-on: https://chromium-review.googlesource.com/442665
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/server/hosts/cros_firmware.py
|
| 077665e8c5dc29c7ddc6cf6a0e13b3a2795d4a25 |
|
30-Nov-2016 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Block automated firmware update on non-managed pools.
After further discussion, it seems that the pools that shouldn't
update firmware is a larger set than merely the FAFT pools. For
now, block automated update in all non-managed pools; this rule may
be relaxed in the near future.
BUG=chromium:611242
TEST=Run repair in a local instance
Change-Id: I311e3037f240e74fd51dcd2904eb8dbc52e72e6c
Reviewed-on: https://chromium-review.googlesource.com/413070
Commit-Ready: Richard Barnette <jrbarnette@google.com>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/hosts/cros_firmware.py
|
| 1bf22a35315b59f202a1e35bd653656d9b25cc94 |
|
19-Nov-2016 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Extract firmware verification into a verifier.
This moves code for firmware verification from the legacy 'cros'
verifier into its own separate verifier, and changes the firmware
repair action to trigger on that verifier, instead of the 'cros'
verifier.
BUG=chromium:633345
TEST=Invoke the new verifier manually at the python CLI
Change-Id: I41b9ea9b62124c56cfbf6037dd9bbec9b6c7fa61
Reviewed-on: https://chromium-review.googlesource.com/413069
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>
/external/autotest/server/hosts/cros_firmware.py
|
| 90ad426740df12555b33813120ca17e140741b78 |
|
18-Nov-2016 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Create a module for cros firmware verification/repair.
This creates a new cros_firmware module for the verifiers and
repair actions associated with firmware on Chrome OS DUTs.
The module contains two classes:
* A verifier for ensuring that firmware is up-to-date on
non-FAFT DUTs in the test lab.
* A repair action to restore known stable firmware on DUTs
used for FAFT.
BUG=None
TEST=Run repair in a local instance
Change-Id: I1857523c048e7277a1132d6e0dad4d5ca9d3b8fb
Reviewed-on: https://chromium-review.googlesource.com/412375
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>
/external/autotest/server/hosts/cros_firmware.py
|