Migrate "ToTAndroidASan" to LUCI |
||||||||||
Issue descriptionMigrate builder chromium.clang:ToTAndroidASan to LUCI. Buildbot: https://ci.chromium.org/buildbot/chromium.clang/ToTAndroidASan LUCI: https://ci.chromium.org/buildbucket/luci.chromium.ci/ToTAndroidASan Migration app will be posting updates on changes of the migration status. For the latest status, see https://luci-migration.appspot.com/masters/chromium.clang/builders/ToTAndroidASan 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 25
Status changed to "Migrated"
,
Jul 26
Not sure what happened here. Migration app should not have marked any of these bugs as fixed. Re-opening and setting to available.
,
Jul 27
,
Dec 7
,
Dec 17
,
Jan 3
Assigned to bpastene to help take a look. Any ideas why we're getting device provisioning issues on the mirrored builder (https://ci.chromium.org/p/chromium/g/luci.chromium.clang/builders)? Thanks!
,
Jan 8
The buildbot version of this bot runs on a machine w/ android devices connected: https://uberchromegw.corp.google.com/i/chromium.clang/buildslaves/build3-b1 The luci version is targeting linux VMs: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/ToTAndroidASan Either the tests on that bot need to be swarmed, or a machine w/ similar devices needs to be added to its pool. Wouldn't that be in the purview of bug 868213?
,
Today
(8 hours ago)
+hinoka to update builder to a swarmed flex bot with Android devices. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by efoo@chromium.org
, Jul 10