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

Issue 842999 link

Starred by 2 users
Status: Assigned
Owner:
█ bmcquade@chromium.org
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"org.chromium.chrome.browser.metrics.UkmTest#testRegularPlusIncognitoCheck" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, May 15 2018 
"org.chromium.chrome.browser.metrics.UkmTest#testRegularPlusIncognitoCheck" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyVAsSBUZsYWtlIklvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIubWV0cmljcy5Va21UZXN0I3Rlc3RSZWd1bGFyUGx1c0luY29nbml0b0NoZWNrDA.

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 lukasza@chromium.org, May 15 2018 

I've attempted to kick-off a FindIt analysis but it didn't work - see  issue 843187

Comment 2 by lukasza@chromium.org, May 15 2018 

java.lang.AssertionError: UKM Enabled:
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertFalse(Assert.java:64)
	at org.chromium.chrome.browser.metrics.UkmTest.testRegularPlusIncognitoCheck(UkmTest.java:124)

Comment 3 by lukasza@chromium.org, May 15 2018

Owner: bmcquade@chromium.org
Status: Assigned (was: Untriaged)
bmcquade@, could you PTAL?  (I've also sent for your review a CL that disables the test)
Project Member

Comment 4 by bugdroid1@chromium.org, May 15 2018 

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

commit 13d4c57629acc54f87f080b3bb292fe2391c4ab0
Author: Lukasz Anforowicz <lukasza@chromium.org>
Date: Tue May 15 18:46:17 2018

Disable flaky testRegularPlusIncognitoCheck test.

Bug: 842999
Change-Id: I97a64b1aa77c2991e0b20e80e985cbd4f7012e02
Tbr: tedchoc@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1060108
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558790}
[modify] https://crrev.com/13d4c57629acc54f87f080b3bb292fe2391c4ab0/chrome/android/javatests/src/org/chromium/chrome/browser/metrics/UkmTest.java

Comment 5 by lukasza@chromium.org, May 15 2018

Labels: -Sheriff-Chromium
Project Member

Comment 6 by chromium...@appspot.gserviceaccount.com, May 16 2018

Labels: Sheriff-Chromium
Detected 5 new flakes for test/step "org.chromium.chrome.browser.metrics.UkmTest#testRegularPlusIncognitoCheck". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyVAsSBUZsYWtlIklvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIubWV0cmljcy5Va21UZXN0I3Rlc3RSZWd1bGFyUGx1c0luY29nbml0b0NoZWNrDA. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Comment 7 by lukasza@chromium.org, May 16 2018

Labels: -Sheriff-Chromium
The last flake reported in #c6 is at 558780 (AFAICT) so still before the CL that disables the test in #c4.  So - I think I can remove the Sheriff-Chromium label again and wait until try flakes system catches up.
►

Sign in to add a comment