Added several new bypass telemetry tests for the data reduction proxy

Added several new bypass telemetry tests for the data reduction proxy

New tests:
- Added new ChromeProxyExplicitBypass integration tests that test "bypass=0", "bypass=<X>", "block=0", and "block=<X>" Chrome-Proxy directives using the test server
- Added new ChromeProxyFallback integration test that gets a "bypass=0" directive from the real data reduction proxy

Cleanup:
- Rewrote the VerifyBadProxies logic, adding support for per-proxy retry times
- Also changed VerifyBadProxies to raise an exception instead of returning false when the actual and expected bad proxy lists were different, which was causing all the existing bypass tests to pass in cases when they should have failed
- Fixed typo in ChromeProxyCorsBypass test, it passes now
- Some general python style cleanup

BUG=374397
Committed: https://crrev.com/f95e460c500507a94f3d20c38bdfd80b254c4d36
Cr-Commit-Position: refs/heads/master@{#300295}

[sclittle, 2014-10-17 22:08:38]

sclittle@chromium.org changed reviewers:
+ bengr@chromium.org, bolian@chromium.org

[sclittle, 2014-10-17 22:08:38]

bolian, bengr: all

With this CL and https://codereview.chromium.org/667463003/, all integration
tests (except for the block-once test of course) pass for me when running on a
local device for both the regular DRP and the dev proxy.

Thanks in advance!

[bengr, 2014-10-17 22:43:34]

On 2014/10/17 22:08:38, sclittle wrote:
> bolian, bengr: all
> 
> With this CL and https://codereview.chromium.org/667463003/, all integration
> tests (except for the block-once test of course) pass for me when running on a
> local device for both the regular DRP and the dev proxy.
> 
> Thanks in advance!

Please be more specific in the CL description about what new tests you've added
and what cleanup was done.

[sclittle, 2014-10-17 23:01:37]

On 2014/10/17 22:43:34, bengr1 wrote:
> On 2014/10/17 22:08:38, sclittle wrote:
> > bolian, bengr: all
> > 
> > With this CL and https://codereview.chromium.org/667463003/, all integration
> > tests (except for the block-once test of course) pass for me when running on
a
> > local device for both the regular DRP and the dev proxy.
> > 
> > Thanks in advance!
> 
> Please be more specific in the CL description about what new tests you've
added
> and what cleanup was done.

Updated CL description with additional details.

[bengr, 2014-10-17 23:24:07]

lgtm, with nits

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
File tools/chrome_proxy/integration_tests/chrome_proxy_measurements.py (right):

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
tools/chrome_proxy/integration_tests/chrome_proxy_measurements.py:116:
"""Correctness measurement for bypass responses."""
Can you be more specific?

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
File
tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/explicit_bypass.py
(right):

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/explicit_bypass.py:12:

comment?

[sclittle, 2014-10-17 23:42:33]

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
File tools/chrome_proxy/integration_tests/chrome_proxy_measurements.py (right):

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
tools/chrome_proxy/integration_tests/chrome_proxy_measurements.py:116:
"""Correctness measurement for bypass responses."""
On 2014/10/17 23:24:07, bengr1 wrote:
> Can you be more specific?

Done.

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
File
tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/explicit_bypass.py
(right):

https://codereview.chromium.org/659333004/diff/20001/tools/chrome_proxy/integ...
tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/explicit_bypass.py:12:

On 2014/10/17 23:24:07, bengr1 wrote:
> comment?

Done.

[bolian, 2014-10-20 06:02:25]

lgtm

[sclittle, 2014-10-20 06:04:05]

The CQ bit was checked by sclittle@chromium.org

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

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/659333004/40001

[commit-bot: I haz the power, 2014-10-20 06:09:20]

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

[commit-bot: I haz the power, 2014-10-20 06:09:20]

Try jobs failed on following builders:
  linux_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu/builds/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/70564)
  android_aosp on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_aosp/bu...)
  android_arm64_dbg_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_arm64_d...)
  android_clang_dbg_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
  linux_chromium_compile_dbg_32 on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  ios_dbg_simulator on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device/bu...)
  ios_rel_device_ninja on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  mac_chromium_compile_dbg on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win8_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...)

[sclittle, 2014-10-20 17:17:34]

The CQ bit was checked by sclittle@chromium.org

[commit-bot: I haz the power, 2014-10-20 17:18:04]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/659333004/60001

[commit-bot: I haz the power, 2014-10-20 17:49:46]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2014-10-20 17:50:24]

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