chrome_proxy_staging.lo_fi.lo_fi failing PrintStep |
|||
Issue descriptionhttps://uberchromegw.corp.google.com/i/internal.client.clank/builders/chrome-proxy-tests First failing build https://uberchromegw.corp.google.com/i/internal.client.clank/builders/chrome-proxy-tests/builds/6057 The only change in the reported range is Proguard change https://chrome-internal-review.googlesource.com/284519. Not sure how that can have caused this though...
,
Sep 8 2016
The speculative revert didn't change anything, should be fine to reland. Looks like the error is: "ChromeProxyMetricException: http://check.googlezip.net/cacheable/test.html: Should have via header 1.1 Chrome-Compression-Proxy-Testing." The error sounds like a systemic issue, but only this one test is affected. I don't have any idea for further action to take as sheriff (not even sure how to disable this kind of test); megjablon@, you added this test originally, could you investigate?
,
Sep 8 2016
Thanks for following up. Relanded it. (https://chrome-internal-review.googlesource.com/#/c/285277/)
,
Sep 8 2016
Looking into this. It may be a server-side issue.
,
Sep 9 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8a4ae2701f7b46969e5b413deb29f751a37d5455 commit 8a4ae2701f7b46969e5b413deb29f751a37d5455 Author: megjablon <megjablon@chromium.org> Date: Fri Sep 09 00:26:04 2016 Use an uncacheable page for the Lo-Fi integration test BUG= 644983 Review-Url: https://codereview.chromium.org/2325843002 Cr-Commit-Position: refs/heads/master@{#417448} [modify] https://crrev.com/8a4ae2701f7b46969e5b413deb29f751a37d5455/tools/chrome_proxy/integration_tests/chrome_proxy_pagesets/lo_fi.py
,
Sep 9 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by agrieve@chromium.org
, Sep 8 2016