In case the title gets changed the test is telemetry.internal.browser.browser_unittest.BrowserTest.testForegroundTab

Additional failures:

- https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/12868
- https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/12857
- https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/12852
- https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/12822
- https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/12798
- https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/12786
- https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/12731

The oldest build # there are still logs for is 12695, and none of the builds between 12731 and 12695 failed so I am hoping the flake was introduced between these two points.

I spent some time trying to get a bisect but haven't had any luck so far (deploying chrome to the VM seems to be very buggy in these revision ranges).

Ned, do you know of any changes that may affect testForegroundTab that landed in the last week?

There is no change that I am aware of. This is probably in the browser side.

This just failed again.

I found this documentation (pasted here for reference), I will see if I can reproduce this locally (but I have no experience with telemetry tests):

https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/docs/run_telemetry_tests.md?q=testForegroundTab&sq=package:chromium&l=20

Hosted docs: https://github.com/catapult-project/catapult/blob/master/telemetry/docs/run_telemetry_tests.md