+mikecase

I think what's happening is that everything now passes through tee.py, which swallows the original return code. Bisect gets the return code of running tee.py, not of the benchmark, which is always successful and so we never end up moving ahead.

Wow, didn't think of this at all. Will work on fix.

I think this simple fix should do the trick.

https://chromium-review.googlesource.com/c/433330/

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build.git/+/2933ae7994ff7089034c13e106c1ba94807cad2d

commit 2933ae7994ff7089034c13e106c1ba94807cad2d
Author: Mike Case <mikecase@google.com>
Date: Fri Jan 27 20:30:44 2017

Fix tee.py eating return code for commands it wraps.

The fact that tee.py always return 0 exit code breaks bisect.

BUG=686080

Change-Id: I2b1904ffafcb2f761c420e211ac597fa6fbec5aa
Reviewed-on: https://chromium-review.googlesource.com/433330
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Michael Case <mikecase@chromium.org>
Commit-Queue: Michael Case <mikecase@chromium.org>

[modify] https://crrev.com/2933ae7994ff7089034c13e106c1ba94807cad2d/scripts/slave/tee.py