I'll add this one too, because the error looks very similar:

https://bugs.chromium.org/p/chromium/issues/detail?id=742083

"IOError: [Errno 2] No such file or directory: 'C:\\b\\c\\b\\win_perf_bisect\\src\\testing\\buildbot\\tryserver.chromium.perf.json'"

Looks like almost all are failing now

Simon, can you help triage? Adding Stephen and Dave in case they have any ideas about where to look for debugging this error.

I think this is completely unrelated to  bug 742422  bug wanted to mention it since we've been seeing mysterious file-doesn't-exist errors multiple times this week.

+dpranke

https://chromium-review.googlesource.com/569444
Hey Dirk, your change removed this file. Looks like we're still using it.
I think we will no longer be using it after the migration to Pinpoint and trybots.py.

For now, I'll upload a patch to re-add it.

Here it is.
https://chromium-review.googlesource.com/c/571858/

Sorry!

Can we change the bisect script to handle this? I'm not sure what an empty {} is used for?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/320a446c373eeb5b42fbe1167adc03f300e7f5a7

commit 320a446c373eeb5b42fbe1167adc03f300e7f5a7
Author: Dave Tu <dtu@chromium.org>
Date: Fri Jul 14 20:13:17 2017

Re-add tryserver.chromium.perf.json.

The file was removed in https://chromium-review.googlesource.com/c/569444/

But tryserver.chromium.perf is still using its custom code path, and not
the standard trybots.py that other tryservers use, so it still requires
tryserver.chromium.perf.json.

I'm in the process of converting it to trybots.py for Pinpoint, and we can
remove it later.

Bug:  742894 
Change-Id: I062de1e561a36b186c20abb071bd5562578a31d1
Reviewed-on: https://chromium-review.googlesource.com/571858
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486861}
[add] https://crrev.com/320a446c373eeb5b42fbe1167adc03f300e7f5a7/testing/buildbot/tryserver.chromium.perf.json

Thanks for the fix, Dave! Is it safe to start re-kicking the blocked bisects now?

Comment 12: Yes, we should be able to get rid of it after the migration to Pinpoint.
Comment 14: Yep!