Issue metadata
Sign in to add a comment
|
Migrate "android_aarch64" to LUCI |
||||||||||||||||||||||||
Issue descriptionMigrate builder client.boringssl:android_aarch64 to LUCI. Buildbot: https://ci.chromium.org/buildbot/client.boringssl/android_aarch64 LUCI: https://ci.chromium.org/buildbucket/luci.boringssl.ci/android_aarch64 Migration app will be posting updates on changes of the migration status. For the latest status, see https://luci-migration.appspot.com/masters/client.boringssl/builders/android_aarch64 Migration app will close this bug when the builder is entirely migrated from Buildbot to LUCI.
,
Jul 10
,
Jul 10
Set priority to 1 for end of Q3 completion of public client migration
,
Jul 24
,
Jul 26
Re-opening to track builders individually to avoid artificially inflating migrated builder count in luci client dashboard. Ryan, please only close these individual when builder is flipped to LUCI.
,
Jul 27
,
Aug 8
Status changed to "Migrated"
,
Aug 10
Labs, mind taking a look at build7-b9? This bot should have devices attached but builds today have been reporting no devices/emulators found. This was a recent bot that Ryan requested to be added to swarming with an Android device attached. CCing Andrii, in case he has some ideas on what's going on.
,
Aug 10
,
Aug 10
,
Aug 10
Fixed by Bev in 873090. Was due to HW failure. Nexus 5x was suffering from familiar bootloop issue. Device replaced.
,
Dec 17
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by efoo@chromium.org
, Jul 9