Seems to be an ancient issue (Apr 25) [1] that was disabled on all platforms and at some point reenabled again. I will disable it and add the previous owners here.


[1] https://github.com/catapult-project/catapult/issues/3510 is linked in the source code: https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/image_processing/screen_finder_unittest.py?q=ScreenFinderTest&sq=package:chromium&l=21

 Issue 773589  has been merged into this issue.

Adding owners/components from related CLs and issue 711307.
Abandoned https://crrev.com/c/712049 and trying to disable the tests according to https://github.com/catapult-project/catapult/blob/master/CONTRIBUTING.md now.

WIP waiting to be landed and rolled out by deps-roller: https://crrev.com/c/712052

 Issue 773477  has been merged into this issue.

Kai worked on getting the numpy and cv2 dependencies correctly downloaded onto test machines. These preexisting tests hadn't run in recent history and it was out of scope to debug them, which is why they were disabled.

The cause of the new failures was https://chromium.googlesource.com/chromium/src/+/5e95315b03684b2f922dc9bd1b9cefe21bb89c30 , which downloaded these binaries onto more machines on the waterfall, implicitly enabling these tests.

fhorschig@, thanks for disabling the tests more broadly. Let me assign this to you to close.

I'm confused ...

nednguyen@ - First, shouldn't we have already been downloading the dependencies on any bot that was running the tests? Second, why is what we run dynamically determined by what we happen to have present on the machine?

actually, those questions are probably better answered in bug 773357 :).