"__main__.InstallerTest.ChromeSystemLevel" is flaky |
||
Issue description"__main__.InstallerTest.ChromeSystemLevel" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMwsSBUZsYWtlIihfX21haW5fXy5JbnN0YWxsZXJUZXN0LkNocm9tZVN5c3RlbUxldmVsDA. 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
,
Jul 26
Chrome is crashing: [6912:2372:0719/050620.875:FATAL:ref_counted.h(61)] Check failed: CalledOnValidSequence(). Someone landed a change that is calling AddRef on some object on the wrong sequence. Since the failures haven't continued, I'm guessing that someone has already fixed or reverted it. Actually, this looks like it was investigated in issue 864915 and has since been fixed. |
||
►
Sign in to add a comment |
||
Comment 1 by yoichio@chromium.org
, Jul 26Labels: -Sheriff-Chromium