OOPIFs: Enable h/t/s/referrer-policy-attribute-import-no-referrer.html test.

OOPIFs: Enable h/t/s/referrer-policy-attribute-import-no-referrer.html test.

This test seemed to have mysteriously "healed" itself.

BUG=680201
Review-Url: https://codereview.chromium.org/2814563002
Cr-Commit-Position: refs/heads/master@{#463823}
Committed: https://chromium.googlesource.com/chromium/src/+/dbdb1d18c66296934a3ec0bd01b0f516030c8fd0

[Łukasz Anforowicz, 2017-04-10 22:01:58]

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

[Łukasz Anforowicz, 2017-04-10 22:01:58]

alexmos@ - could you PTAL?

I see in the bug that 3 people have not been able to repro locally.  OTOH, there
are 3 green linux_site_isolation try jobs in this CL - is that enough to
conclude that the test "healed" itself and will continue to pass on the bot?

FWIW, I tried looking at the flakines dashboard and the test seems to be passing
everywhere, but there are some "CRASH PASS" results on linux_site_isolation.

WDYT?  What should the next steps be?:
- Land this CL?
- Or copy&paste notes from above into the bug and attempt to understand why the
bot behaves differently?

[alexmos, 2017-04-10 23:37:59]

On 2017/04/10 22:01:58, Łukasz A. wrote:
> alexmos@ - could you PTAL?
> 
> I see in the bug that 3 people have not been able to repro locally.  OTOH,
there
> are 3 green linux_site_isolation try jobs in this CL - is that enough to
> conclude that the test "healed" itself and will continue to pass on the bot?
> 
> FWIW, I tried looking at the flakines dashboard and the test seems to be
passing
> everywhere, but there are some "CRASH PASS" results on linux_site_isolation.
> 
> WDYT?  What should the next steps be?:
> - Land this CL?
> - Or copy&paste notes from above into the bug and attempt to understand why
the
> bot behaves differently?

LGTM, I'd say let's re-enable the test and see what happens. :)  If it starts
failing again then we'll at least have more recent data about it and can try to
put in some instrumentation to see how the behavior on the bots is different.  I
agree it seems to have mostly healed itself, though I don't understand why it
isn't showing up in the "expected to fail but passed" list on our FYI bots
(before our recent infra problems, e.g. in
https://storage.googleapis.com/chromium-layout-test-archives/Site_Isolation_W...)

[Łukasz Anforowicz, 2017-04-11 21:53:22]

The CQ bit was checked by lukasza@chromium.org

[commit-bot: I haz the power, 2017-04-11 21:54: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-04-11 23:10:04]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1491947602682420, "parent_rev":
"4f5539045e3c3eea9197ff328302d8dac89a6711", "commit_rev":
"dbdb1d18c66296934a3ec0bd01b0f516030c8fd0"}

[commit-bot: I haz the power, 2017-04-11 23:11:06]

Description was changed from

==========
OOPIFs: Enable h/t/s/referrer-policy-attribute-import-no-referrer.html test.

This test seemed to have mysteriously "healed" itself.

BUG=680201
==========

to

==========
OOPIFs: Enable h/t/s/referrer-policy-attribute-import-no-referrer.html test.

This test seemed to have mysteriously "healed" itself.

BUG=680201

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

[commit-bot: I haz the power, 2017-04-11 23:11:09]

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