chromium.fyi: Increase timeout for linux_layout_tests_layout_ng

chromium.fyi: Increase timeout for linux_layout_tests_layout_ng

BUG=734467, 703894, 524758
NOTRY=true
TBR=qyearsley@chromium.org,ikilpatrick@chromium.org,kojii@chromium.org,eae@chromium.org,dpranke@chromium.org,mcgreevy@chromium.org

Review-Url: https://codereview.chromium.org/2951633002
Cr-Commit-Position: refs/heads/master@{#480650}
Committed: https://chromium.googlesource.com/chromium/src/+/ee2d0f36c75e78a4613e8217a3c8ef6be4def5db

[mithro, 2017-06-19 22:57:56]

The CQ bit was checked by tansell@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-06-19 22:58:22]

Dry run: CQ is trying da patch.

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

[mithro, 2017-06-19 23:44:18]

Description was changed from

==========
chromium.fyi: Increase timeout for linux_layout_tests_layout_ng

BUG=734467,703894,524758
TBR=qyearsley@chromium.org,ikilpatrick@chromium.org,kojii@chromium.org,eae@ch...
==========

to

==========
chromium.fyi: Increase timeout for linux_layout_tests_layout_ng

BUG=734467,703894,524758
NOTRY=true
TBR=qyearsley@chromium.org,ikilpatrick@chromium.org,kojii@chromium.org,eae@ch...
==========

[mithro, 2017-06-19 23:44:25]

The CQ bit was unchecked by tansell@chromium.org

[mithro, 2017-06-19 23:44:32]

The CQ bit was checked by tansell@chromium.org

[commit-bot: I haz the power, 2017-06-19 23:45:22]

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, 2017-06-19 23:50:44]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1497915872105930, "parent_rev":
"31838966b5c1c3e7bf7a02737b94c7393d376393", "commit_rev":
"19729bed1b78abb4eb8c6d8c86467208a0568ab6"}

[commit-bot: I haz the power, 2017-06-19 23:51:02]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1497915872105930, "parent_rev":
"2686d795f8f89d0dffd43d2d426e358d488866da", "commit_rev":
"ee2d0f36c75e78a4613e8217a3c8ef6be4def5db"}

[commit-bot: I haz the power, 2017-06-19 23:51:12]

Description was changed from

==========
chromium.fyi: Increase timeout for linux_layout_tests_layout_ng

BUG=734467,703894,524758
NOTRY=true
TBR=qyearsley@chromium.org,ikilpatrick@chromium.org,kojii@chromium.org,eae@ch...
==========

to

==========
chromium.fyi: Increase timeout for linux_layout_tests_layout_ng

BUG=734467,703894,524758
NOTRY=true
TBR=qyearsley@chromium.org,ikilpatrick@chromium.org,kojii@chromium.org,eae@ch...

Review-Url: https://codereview.chromium.org/2951633002
Cr-Commit-Position: refs/heads/master@{#480650}
Committed:
https://chromium.googlesource.com/chromium/src/+/ee2d0f36c75e78a4613e8217a3c8...
==========

[commit-bot: I haz the power, 2017-06-19 23:51:14]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/ee2d0f36c75e78a4613e8217a3c8...

[Dirk Pranke, 2017-06-19 23:54:13]

This CL doesn't seem to make sense, and I'm not sure why it was TBR'ed?

Why would you increase *both* the number of shards that you're using, *and* the
timeout. And, why such a huge timeout? Now you can potentially lock up 15
different bots for a hundred minutes each, and that seems bad?

[mithro, 2017-06-20 00:35:47]

On 2017/06/19 23:54:13, Dirk Pranke wrote:
> This CL doesn't seem to make sense, and I'm not sure why it was TBR'ed?
> 
> Why would you increase *both* the number of shards that you're using, *and*
the
> timeout. And, why such a huge timeout? Now you can potentially lock up 15
> different bots for a hundred minutes each, and that seems bad?

I'm setting the numbers larger than I think are needed to see if it makes the
bot go green. If things are good we can see what the value should actually be.

[mithro, 2017-06-21 04:24:58]

Patchset #2 (id:20001) has been deleted