Updating both FW_RW and FW_RO failed with "provision_FirmwareUpdate already exists" |
||||
Issue descriptionBoth provisions use the same test, provision_FirmwareUpdate, therefore, in the provision special task, they both try to save results to folder provision_FirmwareUpdate. This conflicts with the autoserv run. We need to force the provision_FirmwareUpdate test to use different result folder name. Or in the worse case, create a new provision_FirmwareROUpdate test for RO update.
,
Apr 8 2016
As it is not called though the control files, it should be the 'tag' in the extra_kwargs argument of the actionables.TestActionable().
,
Apr 12 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/61e407ce852ac90b9b9962347e1d566f9d724e1c commit 61e407ce852ac90b9b9962347e1d566f9d724e1c Author: Dan Shi <dshi@google.com> Date: Fri Apr 08 21:21:07 2016 [autotest] Add tag rw_only to provision_FirmwareUpdate test for RW provision job This is to make sure provision_FirmwareUpdate for RW only update saves result to a different folder other than provision_FirmwareUpdate. So a single provision job can update RO and RW to different build. BUG= chromium:601861 TEST=local test Change-Id: Ief8824c394a4d8d62929a5e42534a6c4887ba5b2 Reviewed-on: https://chromium-review.googlesource.com/338040 Commit-Ready: Dan Shi <dshi@google.com> Tested-by: Dan Shi <dshi@google.com> Reviewed-by: Wai-Hong Tam <waihong@chromium.org> Reviewed-by: Dan Shi <dshi@google.com> [modify] https://crrev.com/61e407ce852ac90b9b9962347e1d566f9d724e1c/server/cros/provision.py
,
Apr 14 2016
Test to know.
,
Apr 14 2016
,
Apr 27 2016
,
Aug 12 2016
Closing. please reopen if its not fixed. |
||||
►
Sign in to add a comment |
||||
Comment 1 by waihong@chromium.org
, Apr 8 2016