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

Issue 860524 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

Wrongly blame 69f98f4c7b8b30b2786fbf525791c38ae0504b38

Project Member Reported by dnicoara@chromium.org, Jul 5

Issue description

Owner: chanli@chromium.org
Status: Started (was: Available)
Thank you for reporting this wrong revert. I'm looking into it.
Looks like Findit only found this commit to be a culprit for test AppsGridViewTest.CloseFolderByClickingBackground in app_list_unittests. But even for this one, looks like still a false positive?


This analysis actually reveals some bugs on UI:
1. Even though try job thought the commit to be a culprit for only one test, on UI the commit was linked to many more tests
2. For  test AppsGridViewTest.CloseFolderByClickingBackground, Good -> Bad build is wrong (test failed at build 28147, then passed at build 28148, then failed at build 28149)


Interestingly, maybe because build 28147 - 28149 all end with 'internal failure', latter build's blamelist includes former build's blamelist, so that could explain why both build 28147 and 28149 were linked to this commit, though this seems buggy as well. 
Components: -Tools>Test>FindIt Tools>Test>FindIt>Autorevert
Labels: Pri-2
Setting defect without priority to Pri-2.

Sign in to add a comment