Various PolicyTest are flaky |
|||
Issue description"ComponentCloudPolicyTest.UpdateExtensionPolicy" 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 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOQsSBUZsYWtlIi5Db21wb25lbnRDbG91ZFBvbGljeVRlc3QuVXBkYXRlRXh0ZW5zaW9uUG9saWN5DA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs This flaky test/step was previously tracked in issue 723548 .
,
May 23 2017
These tests are all failing with errors about pre-existing policies:
[2052:3856:0522/114833.450:WARNING:policy_test_utils.cc(54)] There are pre-existing policies in this machine: {
"StringPolicy": "hklm"
}
e:\b\c\b\win\src\chrome\browser\policy\cloud\component_cloud_policy_browsertest.cc(126): error: Value of: PolicyServiceIsEmpty(g_browser_process->policy_service())
Actual: false
Expected: true
Pre-existing policies in this machine will make this test fail.
Assigning to troopers to see if something is wrong with these machines?
,
May 23 2017
This should be fixed now. There was indeed something wrong with the bots and they've since been reimaged. |
|||
►
Sign in to add a comment |
|||
Comment 1 by mek@chromium.org
, May 23 2017