Mac_android is blocking presubmit due mac-39 being quarantined

[CaseyHillers]

https://chromium-swarm.appspot.com/bot?id=flutter-devicelab-mac-39

Device healthcheck failed: attached_device: No device is available;

Example PR: #96551

[CaseyHillers]

The CL to add some more bots has landed which should unblock developers. This bot still requires recovery.

[yusuf-goog]

Will take a look at the bot when I'm in the lab.

[yusuf-goog]

I checked the device attached to mac-39 and it seems to be working correctly. Unsure if it ran out of power and had to recharge itself. Have noticed recently that a couple ios devices have had their battery die. Might be a cable issue. New cables are on their way.

[yusuf-goog]

mac-39 was mis-assigned to an android pool, but its actually got an ios device connected. Reassigning it to ios staging pool.

[yusuf-goog]

https://chrome-internal-review.googlesource.com/c/infradata/config/+/4474239

[CaseyHillers]

Update: mac 39 is not coming back online due to some json parsing issues

[keyonghan]

From swarming log, get_dimensions() returns

109 2022-02-04 00:41:54.745 I: device_ids: []

This means no device is detected from swarming server. This is also validated on the bot page, where no device dimensions. See the one for mac-40

This explains why the bot is quarantined due to json parse error as no healthcheck_data is returned and hit the value exception: https://chrome-internal.git.corp.google.com/infradata/config/+/refs/heads/main/configs/chromium-swarm/scripts/flutter_ios_staging.py#111.

@yusuf-goog could you double check how the binaries like idevice_id etc, was installed on mac39, and how is it different from other staging bots?

[godofredoc]

This is because idevice_id was installed using mac ports in /usr/local/bin which is not in the bots path. Uninstalled the mac port to allow salt to reinstall it with brew

[keyonghan]

New idevice_id was picked up, but we need to add the device to the provisioning profile.

Quarantined: Device healthcheck failed: codesigning_cert: 0 valid identities found;device_provisioning_profile: device does not exist in the provisioning profile;