from jrbarnette@

The test lab performs automated firmware updates on the DUT fleet based on the way that firmware is built into release build. Given that there are likely to be changes, we'll also need to change the update code.


Two key references:

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/server/hosts/cros_firmware.py?l=161

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/site_utils/stable_images/assign_stable_images.py

The first reference is responsible for reading the Autotest database to determine "what firmware should this DUT have?", and then determining how to install that firmware.

The second reference is code that runs periodically to update the database.

There's also code in chromite that would likely be affected.