There was no output produced for the tests, therefore the bisect job bailed out after 1hr waiting for test output.

https://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6494/steps/steps/logs/stdio

command timed out: 3600 seconds without output, attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=7417.787167

This is not bisect timing out, it is buildbot. Buildbot steps by default time out after one hour if no output is produced. I once tried to find how this timeout could be overriden and I didn't get anywhere.

Another option would be for run_benchmark to output a heartbeat every < 1 hr to stderr (I believe that would be enough for the step to stay alive)

FYI, there is some info about timeouts here: https://github.com/catapult-project/catapult/issues/2254

Annie: I think you reference the wrong timeout bug?

No, it's the correct bug. It's about catapult, and about reducing timeouts, but riannucci's comments are about buildbot in general. I think the relevant bit is that the main way to tweak we have for timeouts is per-builder config, which isn't great.

Hey Roberto, can you please take a look at this, I think we might need to modify master config for this.