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

Issue 902092 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: ----



Sign in to add a comment

[Findit] Flake Detection - Wrong result for org.chromium.chrome.browser.feature_engagement.ScreenshotTabObserverTest

Project Member Reported by petewil@chromium.org, Nov 5

Issue description

Chrome Version: (copy from chrome://version)
OS: (e.g. Win10, MacOS 10.12, etc...)

We got an automatically filed bug that one of our tests was flaky. (https://bugs.chromium.org/p/chromium/issues/detail?id=902046#c1)

When I dug into the results, it seems that they were all from trybots, and trying a patch that was not in our code, and there were many failures instead of just our test.

The text also said that our test passed without the change.


What is the expected result?
no bug for a flaky test

What happens instead?
bug above got filed.



Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
Hi petewil@, it looks this test failed in several try jobs for different CLs. And without any change on those CLs, they got landed later: that's why we think the test is flaky.

I agree that there are multiple failed tests in some of the try jobs and we should file one bug for all those failed tests: we are currently working on it.

Sign in to add a comment