I think https://codereview.chromium.org/2048233002 may have started causing chrome_proxy tests to fail.
From https://uberchromegw.corp.google.com/i/internal.client.clank/builders/chrome-proxy-tests/builds/4925/steps/chrome_proxy.lo_fi.cache_lo_fi_disabled/logs/stdio
(INFO) 2016-06-13 08:00:51,207 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/chrome-proxy-tests/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 03b30820f0e944a4 shell '( ndc resolver flushdefaultif );echo %$?'
Traceback (most recent call last):
File "/b/build/slave/chrome-proxy-tests/build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 84, in _RunStoryAndProcessErrorIfNeeded
state.RunStory(results)
File "/b/build/slave/chrome-proxy-tests/build/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 308, in RunStory
self._current_page, self._current_tab, results)
File "/b/build/slave/chrome-proxy-tests/build/src/tools/chrome_proxy/common/chrome_proxy_measurements.py", line 109, in ValidateAndMeasurePage
self.AddResults(tab, results)
File "/b/build/slave/chrome-proxy-tests/build/src/tools/chrome_proxy/integration_tests/chrome_proxy_measurements.py", line 301, in AddResults
self._metrics.AddResultsForLoFiCache(tab, results, self._is_lo_fi_enabled)
File "/b/build/slave/chrome-proxy-tests/build/src/tools/chrome_proxy/integration_tests/chrome_proxy_metrics.py", line 280, in AddResultsForLoFiCache
'' if is_lo_fi else 'not'))
ChromeProxyMetricException: http://check.googlezip.net/cacheable/image1.png: LoFi expected in response header.
Comment 1 by tbansal@chromium.org
, Jun 13 2016Status: Started (was: Assigned)