In webkitpy/common/net/git_cl.py, print rather than log "waiting" message.

In webkitpy/common/net/git_cl.py, print rather than log "waiting" message.

Reason: In the recent w3c-test-autoroller jobs (e.g.
https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller/builds/6930),
the update wpt step is timing out after 40 minutes with no output after
print "Triggering try jobs".

I believe that this started happening after http://crrev.com/2265603003,
which made it so that when waiting for try job results it uses log.info
rather than print.

BUG=629275
Committed: https://crrev.com/b6cc4b6ed72adabac176e3acc5a41c048de65e8a
Cr-Commit-Position: refs/heads/master@{#415055}

[qyearsley, 2016-08-29 18:04:54]

qyearsley@chromium.org changed reviewers:
+ dpranke@chromium.org

[Dirk Pranke, 2016-08-29 18:07:20]

lgtm

[qyearsley, 2016-08-29 18:09:01]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2016-08-29 18:26:06]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-30 03:45:56]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-30 03:48:17]

Description was changed from

==========
In webkitpy/common/net/git_cl.py, print rather than log "waiting" message.

Reason: In the recent w3c-test-autoroller jobs (e.g.
https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller...),
the update wpt step is timing out after 40 minutes with no output after
print "Triggering try jobs".

I believe that this started happening after http://crrev.com/2265603003,
which made it so that when waiting for try job results it uses log.info
rather than print.

BUG=629275
==========

to

==========
In webkitpy/common/net/git_cl.py, print rather than log "waiting" message.

Reason: In the recent w3c-test-autoroller jobs (e.g.
https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller...),
the update wpt step is timing out after 40 minutes with no output after
print "Triggering try jobs".

I believe that this started happening after http://crrev.com/2265603003,
which made it so that when waiting for try job results it uses log.info
rather than print.

BUG=629275

Committed: https://crrev.com/b6cc4b6ed72adabac176e3acc5a41c048de65e8a
Cr-Commit-Position: refs/heads/master@{#415055}
==========

[commit-bot: I haz the power, 2016-08-30 03:48:18]

Patchset 1 (id:??) landed as
https://crrev.com/b6cc4b6ed72adabac176e3acc5a41c048de65e8a
Cr-Commit-Position: refs/heads/master@{#415055}