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

Issue 854294 link

Starred by 2 users
Status: Duplicate
Merged: issue 851236
Owner:
█ holte@chromium.org
Last visit > 30 days ago
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"SitePerProcessInteractiveBrowserTest.FullscreenElementInABAAndExitViaEscapeKey" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 19 2018 
"SitePerProcessInteractiveBrowserTest.FullscreenElementInABAAndExitViaEscapeKey" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyWQsSBUZsYWtlIk5TaXRlUGVyUHJvY2Vzc0ludGVyYWN0aXZlQnJvd3NlclRlc3QuRnVsbHNjcmVlbkVsZW1lbnRJbkFCQUFuZEV4aXRWaWFFc2NhcGVLZXkM.

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 647549 .

Comment 1 by holte@chromium.org, Jun 19 2018

Owner: sky@chromium.org
Status: Assigned (was: Untriaged)
See also crbug.com/851236
Project Member

Comment 2 by bugdroid1@chromium.org, Jun 19 2018 

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

commit 3dde5ce008d32ca5e939211b175e05dbf5b0beff
Author: Steven Holte <holte@google.com>
Date: Tue Jun 19 23:12:51 2018

Disable FullscreenElementInABAAndExitViaEscapeKey test.

TBR=sky
NOTRY=true

Bug:  854294 
Change-Id: Ic904d41cbc236a8812472e7f0dba0cb45396f256
Reviewed-on: https://chromium-review.googlesource.com/1107135
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568633}
[modify] https://crrev.com/3dde5ce008d32ca5e939211b175e05dbf5b0beff/chrome/browser/site_per_process_interactive_browsertest.cc

Comment 3 by sky@chromium.org, Jun 19 2018

Owner: holte@chromium.org
Why are you assigning this to me?

Comment 4 by holte@chromium.org, Jun 19 2018 

I assigned it to you because crbug/851236 is assigned to you, and I'm fairly certain that it's actually the same bug.

Comment 5 by holte@chromium.org, Jun 19 2018

Labels: -Sheriff-Chromium Test-Disabled
Mergedinto: 851236
Status: Duplicate (was: Assigned)
FullscreenElementInABAAndExitViaEscapeKey and FullscreenElementInABAAndExitViaJS seem to be almost the same test, and both crash on

[28079:28079:0618/213156.625517:FATAL:delegated_frame_host.cc(387)] Check failed: CanCopyFromCompositingSurface().

I'm just going to mark this as a duplicate.
►

Sign in to add a comment