bisect_builds: Don't print '()' after every completed download.

bisect_builds: Don't print '()' after every completed download.

BUG=none
TEST=none


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107301

[Nico, 2011-10-25 19:51:36]

`print()` prints '()' in python.

First to review wins!

[Robert Sesek, 2011-10-25 19:53:04]

lgtm

[commit-bot: I haz the power, 2011-10-25 19:57:55]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/thakis@chromium.org/8395015/1

[szager, 2011-10-25 20:09:50]

Um... no.  'print' without parentheses is a no-op.  If that's what you want, use
'pass' instead.

[Nico, 2011-10-25 20:11:17]

On 2011/10/25 20:09:50, szager wrote:
> Um... no.  'print' without parentheses is a no-op.  If that's what you want,
use
> 'pass' instead.

'print' without parentheses prints a newline and isn't a no-op.

[Nico, 2011-10-25 20:11:39]

(`print,` is a no-op)

[szager, 2011-10-25 20:14:09]

I stand corrected!  python is weird.

On Tue, Oct 25, 2011 at 1:11 PM,  <thakis@chromium.org> wrote:
> (`print,` is a no-op)
>
> http://codereview.chromium.org/8395015/
>

[commit-bot: I haz the power, 2011-10-25 22:49:10]

List of reviewers changed. szager@google.com did a drive-by without LGTM'ing!

[commit-bot: I haz the power, 2011-10-25 22:50:13]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/thakis@chromium.org/8395015/1

[commit-bot: I haz the power, 2011-10-26 00:20:17]

Can't apply patch for file tools/bisect-builds.py.
While running patch -p1 --forward --force;
patching file tools/bisect-builds.py
Hunk #1 FAILED at 229.
1 out of 1 hunk FAILED -- saving rejects to file tools/bisect-builds.py.rej

[commit-bot: I haz the power, 2011-10-26 00:23:12]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/thakis@chromium.org/8395015/4002

[commit-bot: I haz the power, 2011-10-26 01:26:37]

The commit queue went berserk retrying too often for a
seemingly flaky test. Builder is mac_rel, revision is 107252, job name
was 8395015-4002 (previous was lost) (previous was lost) (previous was lost)
(previous was lost).

[M-A Ruel, 2011-10-26 01:35:31]

On 2011/10/26 01:26:37, I haz the power (commit-bot) wrote:
> The commit queue went berserk retrying too often for a
> seemingly flaky test. Builder is mac_rel, revision is 107252, job name
> was 8395015-4002 (previous was lost) (previous was lost) (previous was lost)
> (previous was lost).

Ugh, looking

[M-A Ruel, 2011-10-26 02:28:13]

On 2011/10/26 01:35:31, Marc-Antoine Ruel wrote:
> On 2011/10/26 01:26:37, I haz the power (commit-bot) wrote:
> > The commit queue went berserk retrying too often for a
> > seemingly flaky test. Builder is mac_rel, revision is 107252, job name
> > was 8395015-4002 (previous was lost) (previous was lost) (previous was lost)
> > (previous was lost).
> 
> Ugh, looking

Bug fixed. Checking the bit.

[commit-bot: I haz the power, 2011-10-26 02:28:24]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/thakis@chromium.org/8395015/4002

[commit-bot: I haz the power, 2011-10-26 05:33:30]

Change committed as 107301