android13/external/chromium-trace/catapult/devil/docs/device_denylist.md

2.2 KiB

Devil: Device Denylist

What is it?

The device denylist is a per-run list of devices detected to be in a known bad state along with the reason they are suspected of being in a bad state (offline, not responding, etc). It is stored as a json file. This gets reset every run during the device recovery step (currently part of bb_device_status_check).

Bots

On bots, this is normally found at //out/bad_devices.json. If you are having problems with denylisted devices locally even though a device is in a good state, you can safely delete this file.

Tools for interacting with device deny list.

You can interact with the device denylist via devil.android.device_denylist. This allows for any interaction you would need with a device denylist:

  • Reading
  • Writing
  • Extending
  • Resetting

An example usecase of this is:

from devil.android import device_denylist

denylist = device_denylist.Denylist(denylist_path)
denylisted_devices = denylist.Read()
for device in denylisted_devices:
  print 'Device %s is denylisted' % device
denylist.Reset()
new_denylist = {'device_id1': {'timestamp': ts, 'reason': reason}}
denylist.Write(new_denylist)
denylist.Extend([device_2, device_3], reason='Reason for denylisting')

Where it is used.

The denylist file path is passed directly to the following scripts in chromium:

The denylist is also used in the following scripts: