Disable 4 PDFExtensionTest test cases as they fail on multiple bots.

Disable 4 PDFExtensionTest test cases as they fail on multiple bots.

BUG=701427
Review-Url: https://codereview.chromium.org/2751973009
Cr-Commit-Position: refs/heads/master@{#457908}
Committed: https://chromium.googlesource.com/chromium/src/+/a5082d6ce45219eba13fae950a5fbdda07fe3442

[krasin1, 2017-03-17 20:42:42]

krasin@chromium.org changed reviewers:
+ jochen@chromium.org

[krasin1, 2017-03-17 20:43:06]

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

[commit-bot: I haz the power, 2017-03-17 20:43:49]

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

[Lei Zhang, 2017-03-17 21:36:13]

thestig@chromium.org changed reviewers:
+ thestig@chromium.org

[Lei Zhang, 2017-03-17 21:36:14]

Do you want to disable only in official builds, or something like that rather
than everywhere? This isn't failing everywhere, right?

[commit-bot: I haz the power, 2017-03-17 22:07:51]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-17 22:07:52]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[krasin1, 2017-03-17 22:34:58]

Description was changed from

==========
Disable 4 PDFExtensionTest test cases as they fail on multiple bots.

BUG=701427
==========

to

==========
Disable 4 PDFExtensionTest test cases as they fail on multiple bots.

BUG=701427
==========

[krasin1, 2017-03-17 22:35:16]

On 2017/03/17 21:36:14, Lei Zhang (super slow) wrote:
> Do you want to disable only in official builds, or something like that rather
> than everywhere? This isn't failing everywhere, right?

This is failing on many configurations, but not all.

My main wish here is to have these tests fixed (the bug is assigned to the test
author), and it seems that disabling the tests everywhere will make it more
probable that the issue will be fixed sooner than later.

Nico, what would be your recommendation in this case?

[krasin1, 2017-03-17 22:35:31]

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

[commit-bot: I haz the power, 2017-03-17 22:36:17]

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

[Lei Zhang, 2017-03-17 22:36:42]

lgtm

I hope we'll just fix it soon.

[krasin1, 2017-03-17 22:37:51]

The CQ bit was unchecked by krasin@chromium.org

[krasin1, 2017-03-17 22:37:58]

The CQ bit was checked by krasin@chromium.org

[commit-bot: I haz the power, 2017-03-17 22:38:21]

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

[Nico, 2017-03-17 22:44:26]

On 2017/03/17 22:35:16, krasin1 wrote:
> On 2017/03/17 21:36:14, Lei Zhang (super slow) wrote:
> > Do you want to disable only in official builds, or something like that
rather
> > than everywhere? This isn't failing everywhere, right?
> 
> This is failing on many configurations, but not all.
> 
> My main wish here is to have these tests fixed (the bug is assigned to the
test
> author), and it seems that disabling the tests everywhere will make it more
> probable that the issue will be fixed sooner than later.
> 
> Nico, what would be your recommendation in this case?

TBH I'd revert the change that added the tests, if they're new.

[krasin1, 2017-03-17 22:53:19]

On 2017/03/17 22:44:26, Nico wrote:
> On 2017/03/17 22:35:16, krasin1 wrote:
> > On 2017/03/17 21:36:14, Lei Zhang (super slow) wrote:
> > > Do you want to disable only in official builds, or something like that
> rather
> > > than everywhere? This isn't failing everywhere, right?
> > 
> > This is failing on many configurations, but not all.
> > 
> > My main wish here is to have these tests fixed (the bug is assigned to the
> test
> > author), and it seems that disabling the tests everywhere will make it more
> > probable that the issue will be fixed sooner than later.
> > 
> > Nico, what would be your recommendation in this case?
> 
> TBH I'd revert the change that added the tests, if they're new.

The tests are not very new. They are added in July 2016.

It's unclear what is even broken, but only these tests seem to be affected by
the issue.

[commit-bot: I haz the power, 2017-03-18 00:12:55]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489790278892000, "parent_rev":
"7a3fcb2ef0b8eb5b737ad64f697ae9bc520a0a95", "commit_rev":
"a5082d6ce45219eba13fae950a5fbdda07fe3442"}

[commit-bot: I haz the power, 2017-03-18 00:14:31]

Description was changed from

==========
Disable 4 PDFExtensionTest test cases as they fail on multiple bots.

BUG=701427
==========

to

==========
Disable 4 PDFExtensionTest test cases as they fail on multiple bots.

BUG=701427

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

[commit-bot: I haz the power, 2017-03-18 00:14:32]

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