Here are the problematic runs for my CL: https://codereview.chromium.org/2511823002/
 http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_tsan_rel_ng/builds/339
 https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_msan_rel_ng/builds/390
 https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_asan_rel_ng/builds/14490

<there is hardly anything I can do with this>

I don't believe this is an infra issue, removing the component.

Feel free to add it back if you believe it's actually an infrastructure issue - please explain the reasons, so we can investigate. Thanks!

brettw@, I wonder if you could take a quick look please?  This smells like a flaky/insufficient build dependency, so I hope that your GN expertise might help here + I see that you did touch tools/xdisplaycheck/BUILD.gn (admittedly more than 2 years ago... :-/ ).

Example isolate failure from https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_rel_ng/builds/321046/steps/isolate%20tests/logs/stdio :

python -u /b/rr/tmpfdBsW4/rw/checkout/scripts/slave/recipe_modules/isolate/resources/isolate.py /b/c/b/linux_chromeos/src/tools/swarming_client batcharchive --dump-json /tmp/tmpX4VRtm.json --isolate-server https://isolateserver.appspot.com --verbose /b/c/b/linux_chromeos/src/out/Release/components_unittests.isolated.gen.json
...
isolate: lstat /b/c/b/linux_chromeos/src/out/Release/xdisplaycheck: no such file or directory

Bumping up the priority, since the failure in #c5 happened on a bot covered by default by CQ.

xdisplaycheck is gone now, so this is moot.