Revert of Fix ineffective --disable-gpu-driver-bug-workarounds

Revert of Fix ineffective --disable-gpu-driver-bug-workarounds (patchset #12 id:220001 of https://codereview.chromium.org/2195743005/ )

Reason for revert:
Still cause failures on Nexus 9 https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%28Nexus%209%29/builds/1410

But this time I think I understand why. It could be because the test should also record the disabled extensions. To re-apply them manually when passing --disable-gpu-driver-bug-workarounds

Original issue's description:
> Fix ineffective --disable-gpu-driver-bug-workarounds
>
> It was hidden to the user since chrome://gpu was not showing
> any workarounds, but they were still applied in the gpu process.
>
> Also add a gpu test that sets
> --disable-gpu-driver-bug-workarounds --use_gpu_driver_workaround_for_testing
> and verifies that the only active workaround is USE_TESTING_GPU_DRIVER_WORKAROUND
> in both browser and gpu processes.
>
> BUG=359367
>
> R=kbr@chromium.org, zmo@chromium.org
>
> TEST=./content/test/gpu/run_gpu_test.py gpu_process --show-stdout --browser=exact --extra-browser-args="--no-sandbox" --browser-executable=./out/build/chrome
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
>
> Committed: https://crrev.com/d18006d595e7b6bf070f9ab9777d353ac8457755
> Committed: https://crrev.com/7eee382917c50ad10a487ef1c1402adc8c84e9fd
> Committed: https://crrev.com/87c144ab365dacd92f2bb7720628e3397a44c2d6
> Cr-Original-Original-Commit-Position: refs/heads/master@{#409197}
> Cr-Original-Commit-Position: refs/heads/master@{#412685}
> Cr-Commit-Position: refs/heads/master@{#412989}

TBR=kbr@chromium.org,zmo@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=359367
Committed: https://crrev.com/d653d1ef060d8febe17987daa8ee8ce52bd01ce3
Cr-Commit-Position: refs/heads/master@{#413091}

[Julien Isorce Samsung, 2016-08-19 05:35:19]

The CQ bit was checked by j.isorce@samsung.com

[Julien Isorce Samsung, 2016-08-19 05:35:20]

Created Revert of Fix ineffective --disable-gpu-driver-bug-workarounds

[commit-bot: I haz the power, 2016-08-19 05:35:47]

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, 2016-08-19 05:36:18]

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

[commit-bot: I haz the power, 2016-08-19 05:36:19]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[mlamouri (slow - plz ping), 2016-08-19 09:03:31]

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

[mlamouri (slow - plz ping), 2016-08-19 09:03:31]

The CQ bit was checked by mlamouri@chromium.org

[mlamouri (slow - plz ping), 2016-08-19 09:03:31]

lgtm

[commit-bot: I haz the power, 2016-08-19 09:03:52]

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, 2016-08-19 09:04:39]

Description was changed from

==========
Revert of Fix ineffective --disable-gpu-driver-bug-workarounds (patchset #12
id:220001 of https://codereview.chromium.org/2195743005/ )

Reason for revert:
Still cause failures on Nexus 9
https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%2...

But this time I think I understand why. It could be because the test should also
record the disabled extensions. To re-apply them manually when passing
--disable-gpu-driver-bug-workarounds

Original issue's description:
> Fix ineffective --disable-gpu-driver-bug-workarounds
> 
> It was hidden to the user since chrome://gpu was not showing
> any workarounds, but they were still applied in the gpu process.
> 
> Also add a gpu test that sets
> --disable-gpu-driver-bug-workarounds --use_gpu_driver_workaround_for_testing
> and verifies that the only active workaround is
USE_TESTING_GPU_DRIVER_WORKAROUND
> in both browser and gpu processes.
> 
> BUG=359367
> 
> R=kbr@chromium.org, zmo@chromium.org
> 
> TEST=./content/test/gpu/run_gpu_test.py gpu_process --show-stdout
--browser=exact --extra-browser-args="--no-sandbox"
--browser-executable=./out/build/chrome
>
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> 
> Committed: https://crrev.com/d18006d595e7b6bf070f9ab9777d353ac8457755
> Committed: https://crrev.com/7eee382917c50ad10a487ef1c1402adc8c84e9fd
> Committed: https://crrev.com/87c144ab365dacd92f2bb7720628e3397a44c2d6
> Cr-Original-Original-Commit-Position: refs/heads/master@{#409197}
> Cr-Original-Commit-Position: refs/heads/master@{#412685}
> Cr-Commit-Position: refs/heads/master@{#412989}

TBR=kbr@chromium.org,zmo@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=359367
==========

to

==========
Revert of Fix ineffective --disable-gpu-driver-bug-workarounds (patchset #12
id:220001 of https://codereview.chromium.org/2195743005/ )

Reason for revert:
Still cause failures on Nexus 9
https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%2...

But this time I think I understand why. It could be because the test should also
record the disabled extensions. To re-apply them manually when passing
--disable-gpu-driver-bug-workarounds

Original issue's description:
> Fix ineffective --disable-gpu-driver-bug-workarounds
> 
> It was hidden to the user since chrome://gpu was not showing
> any workarounds, but they were still applied in the gpu process.
> 
> Also add a gpu test that sets
> --disable-gpu-driver-bug-workarounds --use_gpu_driver_workaround_for_testing
> and verifies that the only active workaround is
USE_TESTING_GPU_DRIVER_WORKAROUND
> in both browser and gpu processes.
> 
> BUG=359367
> 
> R=kbr@chromium.org, zmo@chromium.org
> 
> TEST=./content/test/gpu/run_gpu_test.py gpu_process --show-stdout
--browser=exact --extra-browser-args="--no-sandbox"
--browser-executable=./out/build/chrome
>
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> 
> Committed: https://crrev.com/d18006d595e7b6bf070f9ab9777d353ac8457755
> Committed: https://crrev.com/7eee382917c50ad10a487ef1c1402adc8c84e9fd
> Committed: https://crrev.com/87c144ab365dacd92f2bb7720628e3397a44c2d6
> Cr-Original-Original-Commit-Position: refs/heads/master@{#409197}
> Cr-Original-Commit-Position: refs/heads/master@{#412685}
> Cr-Commit-Position: refs/heads/master@{#412989}

TBR=kbr@chromium.org,zmo@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=359367
==========

[commit-bot: I haz the power, 2016-08-19 09:04:40]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-19 09:07:07]

Description was changed from

==========
Revert of Fix ineffective --disable-gpu-driver-bug-workarounds (patchset #12
id:220001 of https://codereview.chromium.org/2195743005/ )

Reason for revert:
Still cause failures on Nexus 9
https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%2...

But this time I think I understand why. It could be because the test should also
record the disabled extensions. To re-apply them manually when passing
--disable-gpu-driver-bug-workarounds

Original issue's description:
> Fix ineffective --disable-gpu-driver-bug-workarounds
> 
> It was hidden to the user since chrome://gpu was not showing
> any workarounds, but they were still applied in the gpu process.
> 
> Also add a gpu test that sets
> --disable-gpu-driver-bug-workarounds --use_gpu_driver_workaround_for_testing
> and verifies that the only active workaround is
USE_TESTING_GPU_DRIVER_WORKAROUND
> in both browser and gpu processes.
> 
> BUG=359367
> 
> R=kbr@chromium.org, zmo@chromium.org
> 
> TEST=./content/test/gpu/run_gpu_test.py gpu_process --show-stdout
--browser=exact --extra-browser-args="--no-sandbox"
--browser-executable=./out/build/chrome
>
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> 
> Committed: https://crrev.com/d18006d595e7b6bf070f9ab9777d353ac8457755
> Committed: https://crrev.com/7eee382917c50ad10a487ef1c1402adc8c84e9fd
> Committed: https://crrev.com/87c144ab365dacd92f2bb7720628e3397a44c2d6
> Cr-Original-Original-Commit-Position: refs/heads/master@{#409197}
> Cr-Original-Commit-Position: refs/heads/master@{#412685}
> Cr-Commit-Position: refs/heads/master@{#412989}

TBR=kbr@chromium.org,zmo@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=359367
==========

to

==========
Revert of Fix ineffective --disable-gpu-driver-bug-workarounds (patchset #12
id:220001 of https://codereview.chromium.org/2195743005/ )

Reason for revert:
Still cause failures on Nexus 9
https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%2...

But this time I think I understand why. It could be because the test should also
record the disabled extensions. To re-apply them manually when passing
--disable-gpu-driver-bug-workarounds

Original issue's description:
> Fix ineffective --disable-gpu-driver-bug-workarounds
>
> It was hidden to the user since chrome://gpu was not showing
> any workarounds, but they were still applied in the gpu process.
>
> Also add a gpu test that sets
> --disable-gpu-driver-bug-workarounds --use_gpu_driver_workaround_for_testing
> and verifies that the only active workaround is
USE_TESTING_GPU_DRIVER_WORKAROUND
> in both browser and gpu processes.
>
> BUG=359367
>
> R=kbr@chromium.org, zmo@chromium.org
>
> TEST=./content/test/gpu/run_gpu_test.py gpu_process --show-stdout
--browser=exact --extra-browser-args="--no-sandbox"
--browser-executable=./out/build/chrome
>
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
>
> Committed: https://crrev.com/d18006d595e7b6bf070f9ab9777d353ac8457755
> Committed: https://crrev.com/7eee382917c50ad10a487ef1c1402adc8c84e9fd
> Committed: https://crrev.com/87c144ab365dacd92f2bb7720628e3397a44c2d6
> Cr-Original-Original-Commit-Position: refs/heads/master@{#409197}
> Cr-Original-Commit-Position: refs/heads/master@{#412685}
> Cr-Commit-Position: refs/heads/master@{#412989}

TBR=kbr@chromium.org,zmo@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=359367

Committed: https://crrev.com/d653d1ef060d8febe17987daa8ee8ce52bd01ce3
Cr-Commit-Position: refs/heads/master@{#413091}
==========

[commit-bot: I haz the power, 2016-08-19 09:07:08]

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