The firmware should be in any cros version > 10895.6.0

+jrbarnette to see if we can get this updated soon.

To dchan@ to specify the target Beta build.

target build m69 is 10895.7.0. Anything M69 or newer will have the right FW.

> target build m69 is 10895.7.0. Anything M69 or newer will have the right FW.

No test ran for that build, so we don't know whether it's good or not:
    https://ubercautotest.corp.google.com/afe/#tab_id=view_job&object_id=221487085

Canary ToT did run and pass.  This is for R70-10922.0.0:
    http://cautotest-prod/afe/#tab_id=view_job&object_id=222192348

That build does contain the requested firmware:
    $ stable_version -n -t cros scarlet R70-10922.0.0
    Dry run; no mappings will be changed.
    Updating  Chrome OS  scarlet      -> R69-10859.0.0 to R70-10922.0.0
    Updating  Firmware   dru          -> Google_Scarlet.10388.52.0 to Google_Scarlet.10388.56.0

Will the canary build do?

I've updated to the canary (R70) build:
$ stable_version -t cros scarlet R70-10922.0.0
Updating  Chrome OS  scarlet      -> R69-10859.0.0 to R70-10922.0.0
Updating  Firmware   dru          -> Google_Scarlet.10388.52.0 to Google_Scarlet.10388.56.0

Using a Beta R69 build in place of a canary build could be useful, but
until such a build has actually run and passed tests, we can use the
current settings.

dchan@ - PTAL, and say if you have a preference.

 seems like  	10895.10.0 would do also
https://cros-goldeneye.corp.google.com/chromeos/console/listBuild?boards=scarlet&milestone=69&chromeOsVersion=&chromeVersion=&startTimeFrom=&startTimeTo=&token=ALuFCnQQoFDVgXZziumpD7urd-JQ%3A1533168952774#%2F

And it has the right firmware, can you update with that version?

The Goldeneye link doesn't prove the right thing.  We need test results
from stainless:
    https://stainless.corp.google.com/search?exclude_cts=true&exclude_non_release=true&suite=%5Ebvt%5C-inline%24&model=%5Edru%24&view=matrix&col=build&row=test&first_date=2018-07-27&last_date=2018-08-02

That shows that there are test results.

$ stable_version -t cros scarlet R69-10895.10.0
Updating  Chrome OS  scarlet      -> R70-10922.0.0 to R69-10895.10.0
Unchanged Firmware   dru          -> Google_Scarlet.10388.56.0

Just checking if this FW update was done on all the Dru DUTs?

Since there is hot-swapping in place for pool:cts, I would recommend to update all the Dru lab DUTs, not just pool:cts. 

Re comment #11:  I've updated the firmware update FAQ to address
this question:
    https://sites.google.com/a/google.com/chromeos/for-team-members/infrastructure/firmware-updates#TOC-What-Devices-Pools-Will-Be-Updated-

Yup, I am aware of weekly FW updates on Tuesday in the lab.

I was just making sure in case this update was triggered manually. 

I did a probe (but can't get to all of them) and looks like all of them are updated.

chromeos2-row1-rack11-host1 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row1-rack11-host5 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row1-rack11-host3 is
chromeos2-row2-rack11-host1 is
chromeos2-row2-rack11-host7 is
chromeos2-row1-rack11-host7 is
chromeos2-row1-rack11-host9 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row1-rack11-host11 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host4 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host5 is
chromeos2-row2-rack11-host6 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host8 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host9 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host10 is
chromeos2-row2-rack11-host11 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host12 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host2 is
chromeos1-row2-rack1-host2 is
chromeos2-row1-rack11-host13 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row1-rack11-host15 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row1-rack11-host17 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.26.0
chromeos2-row1-rack11-host19 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host14 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host16 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host18 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host13 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host15 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host17 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos2-row2-rack11-host19 is Google_Scarlet.10388.26.0 Google_Scarlet.10388.56.0
chromeos15-row4-rack12-host7 is


I think the biggest problem is still the lack of devices in the lab
listlabel scarlet
     10 bvt
      1 crosperf
      6 cts
      1 faft-cr50
      3 faft-test
      8 suites
      1 wificell