New issue
Advanced search Search tips

Issue 708612 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"TabScrubberTest.FullScreenBrowser" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Apr 5 2017

Issue description

"TabScrubberTest.FullScreenBrowser" 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 5 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLAsSBUZsYWtlIiFUYWJTY3J1YmJlclRlc3QuRnVsbFNjcmVlbkJyb3dzZXIM.

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
 
Owner: benjhayden@chromium.org
Owner: ----
Labels: -Sheriff-Chromium
Owner: afakhry@chromium.org
Disabling the test as it is flaky.
Removing Sheriff-Chromium as the test is now disabled and assigned.
Project Member

Comment 4 by bugdroid1@chromium.org, Apr 6 2017

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

commit b6633e1e1e2045a0a8c742445d75c87a3bc0e47b
Author: kelvinp <kelvinp@chromium.org>
Date: Thu Apr 06 00:43:26 2017

Disable flaky TabScrubberTest.FullScreenBrowser in interactive_ui_tests

BUG= 708612 
TBR=afakhry

Review-Url: https://codereview.chromium.org/2802873002
Cr-Commit-Position: refs/heads/master@{#462298}

[modify] https://crrev.com/b6633e1e1e2045a0a8c742445d75c87a3bc0e47b/chrome/browser/ui/views/ash/tab_scrubber_browsertest.cc

Cc: afakhry@chromium.org
Owner: weidongg@chromium.org
Status: Assigned (was: Untriaged)
I run the test locally, it keeps waiting for the tabstrip to go into immersive mode and the mouse cursor is above the tabstrip.
IMO, one simple solution is to initialize the mouse position to make it away from the tabstrip.
Project Member

Comment 7 by bugdroid1@chromium.org, Apr 26 2017

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

commit c1f175f856da8298510aa3085b194342c00dfc7d
Author: weidongg <weidongg@chromium.org>
Date: Wed Apr 26 02:25:00 2017

Fix test TabScrubberTest.FullScreenBrowser

The test times out due to the interference of mouse. When a mouse
hovers above the tab strip, the immersive mode reveal never ends.
Solution is to initialize the mouse position to make it away from
the tabstrip.

BUG= 708612 
TEST=interactive_ui_tests
--gtest_filter=TabScrubberTest.FullScreenBrowser

Review-Url: https://codereview.chromium.org/2842553005
Cr-Commit-Position: refs/heads/master@{#467206}

[modify] https://crrev.com/c1f175f856da8298510aa3085b194342c00dfc7d/chrome/browser/ui/views/ash/tab_scrubber_browsertest.cc

Status: Fixed (was: Assigned)

Sign in to add a comment