New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 606574 link

Starred by 1 user
Status: Assigned
Owner:
rdevlin....@chromium.org
Cc:
█ mgiuca@chromium.org
jyasskin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"DeclarativeContentApiTest.Overview" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Apr 25 2016 
"DeclarativeContentApiTest.Overview" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLQsSBUZsYWtlIiJEZWNsYXJhdGl2ZUNvbnRlbnRBcGlUZXN0Lk92ZXJ2aWV3DA.

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

Comment 1 by creis@chromium.org, Apr 25 2016

Owner: jyasskin@chromium.org
jyasskin: Can you take a look?  Looks like you added this test in http://codereview.chromium.org/11547033.

try run at 2016-04-25 21:41:40 UTC	patchset	win_chromium_x64_rel_ng	(reported in 606574)
try run at 2016-04-25 19:09:20 UTC	patchset	win_chromium_x64_rel_ng	(reported in 606574)
try run at 2016-04-25 17:45:30 UTC	patchset	win_chromium_x64_rel_ng	(reported in 606574)
 
try run at 2016-03-01 23:18:49 UTC	patchset	linux_chromium_chromeos_rel_ng	
try run at 2015-09-18 23:34:26 UTC	patchset	win_chromium_x64_rel_ng	
try run at 2015-05-08 19:54:47 UTC	patchset	mac_chromium_rel_ng	
try run at 2015-03-25 03:25:48 UTC	patchset	linux_chromium_asan_rel	
try run at 2014-12-16 10:09:47 UTC	patchset	win_chromium_rel_ng	


DeclarativeContentApiTest.Overview (run #1):
[ RUN      ] DeclarativeContentApiTest.Overview
e:uild\slave\winuild\src\chromerowser\extensionspi\declarative_content\declarative_content_apitest.cc(312): error: Value of: page_action->GetIsVisible(tab_id)
  Actual: false
Expected: true
Adding a matching element should show the page action.
[  FAILED  ] DeclarativeContentApiTest.Overview, where TypeParam =  and GetParam() =  (737 ms)

Comment 2 by mgiuca@chromium.org, Apr 26 2016

Cc: mgiuca@chromium.org
Status: Assigned (was: Untriaged)
I am disabling this test: https://codereview.chromium.org/1918133002
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 26 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6f5ab0ebe4c17d52a447ca7a1653425a2498805c

commit 6f5ab0ebe4c17d52a447ca7a1653425a2498805c
Author: mgiuca <mgiuca@chromium.org>
Date: Tue Apr 26 02:19:55 2016

Disable DeclarativeContentApiTest.Overview (flaky).

TBR=jyasskin@chromium.org
BUG=606574

Review URL: https://codereview.chromium.org/1918133002

Cr-Commit-Position: refs/heads/master@{#389667}

[modify] https://crrev.com/6f5ab0ebe4c17d52a447ca7a1653425a2498805c/chrome/browser/extensions/api/declarative_content/declarative_content_apitest.cc

Comment 4 by mgiuca@chromium.org, Apr 26 2016

Labels: -Sheriff-Chromium

Comment 5 by jyasskin@chromium.org, Apr 26 2016

Cc: jyasskin@chromium.org
Owner: rdevlin....@chromium.org
I'm not likely to get a chance to look at this soon. Did it get flaky suddenly, or has it been flaky for its whole life, and we only now have a good enough flakiness-detector-bot to notice?

Comment 6 by mgiuca@chromium.org, Apr 27 2016 

It looks like it just started flaking yesterday (3 occurrences).
►

Sign in to add a comment