Timeout expectation for h/t/s/mc/active-subresource-in-http-iframe-not-blocked.https.html.

Timeout expectation for h/t/s/mc/active-subresource-in-http-iframe-not-blocked.https.html.

This is a new test introduced in https://codereview.chromium.org/1731103007.

BUG=590773
TBR=estark@chromium.org

Committed: https://crrev.com/407b7d53c40b10d3940b44282352e9e49b0cec6b
Cr-Commit-Position: refs/heads/master@{#378320}

[Łukasz Anforowicz, 2016-02-29 17:28:01]

lukasza@chromium.org changed reviewers:
+ estark@chromium.org

[Łukasz Anforowicz, 2016-02-29 17:28:01]

Emily, could you please take a look?

[Łukasz Anforowicz, 2016-02-29 21:11:54]

Description was changed from

==========
Timeout expectation for
h/t/s/mc/active-subresource-in-http-iframe-not-blocked.https.html.

This is a new test introduced in https://codereview.chromium.org/1731103007.

BUG=590773
==========

to

==========
Timeout expectation for
h/t/s/mc/active-subresource-in-http-iframe-not-blocked.https.html.

This is a new test introduced in https://codereview.chromium.org/1731103007.

BUG=590773
TBR=estark@chromium.org
==========

[Łukasz Anforowicz, 2016-02-29 21:12:44]

The CQ bit was checked by lukasza@chromium.org

[commit-bot: I haz the power, 2016-02-29 21:13:11]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1746083002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1746083002/1

[estark, 2016-02-29 21:15:34]

lgtm (I'm trying to figure out why is timing out right now)

[commit-bot: I haz the power, 2016-02-29 23:56:21]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-29 23:57:35]

Description was changed from

==========
Timeout expectation for
h/t/s/mc/active-subresource-in-http-iframe-not-blocked.https.html.

This is a new test introduced in https://codereview.chromium.org/1731103007.

BUG=590773
TBR=estark@chromium.org
==========

to

==========
Timeout expectation for
h/t/s/mc/active-subresource-in-http-iframe-not-blocked.https.html.

This is a new test introduced in https://codereview.chromium.org/1731103007.

BUG=590773
TBR=estark@chromium.org

Committed: https://crrev.com/407b7d53c40b10d3940b44282352e9e49b0cec6b
Cr-Commit-Position: refs/heads/master@{#378320}
==========

[commit-bot: I haz the power, 2016-02-29 23:57:36]

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

[estark, 2016-02-29 23:58:31]

I think this should actually go in the
"testRunner.setAllowDisplayOfInsecureContent is not replicated to OOPIFs"
section?

[Łukasz Anforowicz, 2016-03-01 00:17:37]

On 2016/02/29 23:58:31, estark wrote:
> I think this should actually go in the
> "testRunner.setAllowDisplayOfInsecureContent is not replicated to OOPIFs"
> section?

Oh, ok - let me fix this in crrev.com/1750073002?

Thanks for digging into the timeout and my apologies for landing the test
expectation in a not-quite-the-right-shape (otoh, hopefully this will make the
bot green again :-).