Revert "Un-blacklist D3D11 on Intel machines."

Revert "Un-blacklist D3D11 on Intel machines."

> With ongoing work on fixing bugs and performance in D3D11, as well
> as blacklisting old drviers, we might have more stable results on
> Intel. If possible we can narrow down ranges of crashing configs
> and blacklist those individually.
>
> BUG=363721
BUG=369475
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=269591

[Jamie Madill, 2014-05-07 21:29:12]

PTAL, are those GPU bot failures to be expected?

[Jamie Madill, 2014-05-08 14:12:35]

Whoops, forgot to add kbr. Ken, please take a look, are those expected gpu bot
fails?

[Ken Russell (switch to Gerrit), 2014-05-08 19:55:16]

On 2014/05/08 14:12:35, Jamie Madill wrote:
> Whoops, forgot to add kbr. Ken, please take a look, are those expected gpu bot
> fails?

Yes, whenever the version is incremented the try jobs will currently fail.
http://crbug.com/349262 tracks this.

[Ken Russell (switch to Gerrit), 2014-05-08 19:56:23]

On 2014/05/08 19:55:16, Ken Russell wrote:
> On 2014/05/08 14:12:35, Jamie Madill wrote:
> > Whoops, forgot to add kbr. Ken, please take a look, are those expected gpu
bot
> > fails?
> 
> Yes, whenever the version is incremented the try jobs will currently fail.
> http://crbug.com/349262 tracks this.

BTW, you could work around this by adding failure expectations in
src/content/test/gpu/gpu_tests/pixel_expectations.py , landing this CL, and then
removing the failure expectations in a subsequent CL. But that shouldn't be
necessary in most cases, I think.

[Jamie Madill, 2014-05-08 19:59:21]

On 2014/05/08 19:56:23, Ken Russell wrote:
> On 2014/05/08 19:55:16, Ken Russell wrote:
> > On 2014/05/08 14:12:35, Jamie Madill wrote:
> > > Whoops, forgot to add kbr. Ken, please take a look, are those expected gpu
> bot
> > > fails?
> > 
> > Yes, whenever the version is incremented the try jobs will currently fail.
> > http://crbug.com/349262 tracks this.
> 
> BTW, you could work around this by adding failure expectations in
> src/content/test/gpu/gpu_tests/pixel_expectations.py , landing this CL, and
then
> removing the failure expectations in a subsequent CL. But that shouldn't be
> necessary in most cases, I think.

ok thanks. should I follow that procedure of does this CL LG?

[Ken Russell (switch to Gerrit), 2014-05-08 20:00:05]

It LGTM. The GPU bot failures won't block the CL right now, though they would in
the future.

[Jamie Madill, 2014-05-08 20:02:39]

The CQ bit was checked by jmadill@chromium.org

[commit-bot: I haz the power, 2014-05-08 20:08:10]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jmadill@chromium.org/273723004/20001

[commit-bot: I haz the power, 2014-05-08 20:27:49]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  android_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/18...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  win_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_compile_...)

[commit-bot: I haz the power, 2014-05-08 20:35:48]

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

[commit-bot: I haz the power, 2014-05-08 20:35:48]

Try jobs failed on following builders:
  android_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/18...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)

[Jamie Madill, 2014-05-09 15:37:21]

The CQ bit was checked by jmadill@chromium.org

[commit-bot: I haz the power, 2014-05-09 15:40:39]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jmadill@chromium.org/273723004/40001

[Jamie Madill, 2014-05-09 20:23:48]

The CQ bit was unchecked by jmadill@chromium.org

[Jamie Madill, 2014-05-09 20:23:57]

The CQ bit was checked by jmadill@chromium.org

[commit-bot: I haz the power, 2014-05-09 20:27:58]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jmadill@chromium.org/273723004/40001

[commit-bot: I haz the power, 2014-05-10 18:22:34]

Change committed as 269591