"compile_v2" is flaky (closure compiler) |
|||
Issue description"compile_v2" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyFQsSBUZsYWtlIgpjb21waWxlX3YyDA.
,
Aug 2 2016
This one https://codereview.chromium.org/2201553002 was an actual issue and not flakiness. CL https://codereview.chromium.org/2180823004/#ps80001 is also on the list of potential flakes and I don't see why it started working for that patch. it was failing with: ## /b/build/slave/linux/build/src/chrome/browser/resources/settings/device_page/device_page.js:111: ERROR - Property setSubpageChain never defined on ? ## this.$.pages.setSubpageChain(['note']); ## ^ and then stopped failing. dpapad@ do you have an idea of what happened there?
,
Aug 2 2016
yep, this was a real failure that made it through try jobs because of a merge conflict |
|||
►
Sign in to add a comment |
|||
Comment 1 by tapted@chromium.org
, Aug 1 2016Components: UI>Browser>WebUI
Labels: -Sheriff-Chromium
Owner: dschuyler@chromium.org
Status: Assigned (was: Untriaged)
Summary: "compile_v2" is flaky (closure compiler) (was: "compile_v2" is flaky)