Wrongly blame 69f98f4c7b8b30b2786fbf525791c38ae0504b38 |
|||
Issue descriptionDetail is https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzY5Zjk4ZjRjN2I4YjMwYjI3ODZmYmY1MjU3OTFjMzhhZTA1MDRiMzgM The reland (https://chromium-review.googlesource.com/c/chromium/src/+/1127220) passes on the linux_chromium_chromeos_asan_rel_ng bot.
,
Jul 6
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.
,
Aug 19
,
Jan 11
Setting defect without priority to Pri-2. |
|||
►
Sign in to add a comment |
|||
Comment 1 by chanli@chromium.org
, Jul 6Status: Started (was: Available)