More recent failures:

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?id=3044793
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8932392667197751936

Those builds failed in cheets_LoginScreen.  

cyan-chrome-pfq: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8932392688903604320

reef-chrome-pfq: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8932392667197751936

As Ryan notes, these are in cheets_LoginScreen

The cyan failure appears to be a real test failure:
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 800, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 464, in execute
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 371, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/cheets_LoginScreen/cheets_LoginScreen.py", line 91, in run_once
    self._test_cpuset()
  File "/usr/local/autotest/tests/cheets_LoginScreen/cheets_LoginScreen.py", line 235, in _test_cpuset
    '{} setting'.format(setting_file))
  File "/usr/local/autotest/tests/cheets_LoginScreen/cheets_LoginScreen.py", line 25, in _assert_eq
    .format(msg, expected, actual))
TestFail: Unexpected /dev/cpuset/foreground/cpus setting: Expected: 0-1, Actual: 0

reef-chrome-pfq has had a series of red runs with cheets failures. Latest:
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8932255668624695376

I'm going to mark the builder experimental.

The cheets_NotificationTest run in #1 failed with "TimeoutError: Timed out waiting for condition: Notification is found". I didn't notice anything suspicious in the Android and Chrome logs. Adding yoshiki@ for awareness of potential flakiness.

Reassigning to yusukes@ for the cheets_LoginScreen failure, based on blame for the trace in #2.

cheets_LoginScreen failure has already been fixed in nyc-mr1-arc, and Android N PFQ  has already picked up the fix in R72-11173.0.0. Is it still failing?

Thanks. The failed runs were on R72-11172.0.0, so I'll close if the next run turns green.

 Issue 896972  has been merged into this issue.