Issue metadata
Sign in to add a comment
|
virtual/user-activation-v2/fast/events/middleClickAutoscroll-latching.html is flaky |
||||||||||||||||||||||
Issue descriptionFlaky test: virtual/user-activation-v2/fast/events/middleClickAutoscroll-latching.html Sample failed build due to flakiness: https://chromium-swarm.appspot.com/task?id=40295c052f110a10 Test output log: https://ci.chromium.org/buildbot/chromium.win/Win7%20Tests%20%28dbg%29%281%29/71796 Culprit (70.0% confidence): https://chromium-review.googlesource.com/q/I2298e9d4a750a50334ae8047bc9f2ee95a750434 Analysis: https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVy5QELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKuAWNocm9taXVtLndpbi9XaW43IFRlc3RzIChkYmcpKDEpLzcxNzk2L3dlYmtpdF9sYXlvdXRfdGVzdHMgKGV4cGVyaW1lbnRhbCkvZG1seWRIVmhiQzkxYzJWeUxXRmpkR2wyWVhScGIyNHRkakl2Wm1GemRDOWxkbVZ1ZEhNdmJXbGtaR3hsUTJ4cFkydEJkWFJ2YzJOeWIyeHNMV3hoZEdOb2FXNW5MbWgwYld3PQwLEhNNYXN0ZXJGbGFrZUFuYWx5c2lzGAEM Please revert the culprit, or disable the test and find the appropriate owner. If the culprit above is wrong, please file a bug using this link: https://bugs.chromium.org/p/chromium/issues/entry?status=Unconfirmed&labels=Pri-1,Test-Findit-Wrong&components=Tools%3ETest%3EFindit%3EFlakiness&summary=%5BFindit%5D%20Flake%20Analyzer%20-%20Wrong%20result%20for%20virtual/user-activation-v2/fast/events/middleClickAutoscroll-latching.html&comment=Link%20to%20Analysis%3A%20https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVy5QELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKuAWNocm9taXVtLndpbi9XaW43IFRlc3RzIChkYmcpKDEpLzcxNzk2L3dlYmtpdF9sYXlvdXRfdGVzdHMgKGV4cGVyaW1lbnRhbCkvZG1seWRIVmhiQzkxYzJWeUxXRmpkR2wyWVhScGIyNHRkakl2Wm1GemRDOWxkbVZ1ZEhNdmJXbGtaR3hsUTJ4cFkydEJkWFJ2YzJOeWIyeHNMV3hoZEdOb2FXNW5MbWgwYld3PQwLEhNNYXN0ZXJGbGFrZUFuYWx5c2lzGAEM
,
Sep 25
I doubt that the CL is related to the observed flakiness: - The CL fixes an oob read (reading past the end of a string). - The test seems unrelated to the CL. - The flakiness mode is weird here - the test went from "always *failing*" to "flakily passing". Can we hold off with the revert and either 1) re-run FindIt's analysis (possibly asking it to either A) run more iterations at each revision or B) run iterations at each of the revisions between r590405 and r590411 (or possibly slightly wider) or 2) disable the test instead (especially since it is under a virtual test suite, so I assume it tests a Blink feature that is not yet enabled by default).
,
Sep 25
I'll take the sheriff label off, it'll get re-added if it detects another flake.
,
Sep 25
I agree with lukasza@. The CL in question fixes logic that shouldn't be invoked in this layout test. Also note that the test is already marked as flaky in TestExpectations, referencing issues 874162 and 827209, so I think this bug should be duped into one of those. Reassigning to sunyunjia@, owner of the latter bug, to confirm.
,
Sep 26
The flake is matching [ Pass Failure ] on Win,Linux so this is probably a timeout issue rather than an explicit failure as a flake.
,
Sep 26
,
Sep 26
Sorry misread these[1] instructions, first time sheriff here, re-adding the Sheriff-Chromium label. [1] http://dev.chromium.org/developers/tree-sheriffs/sheriffing-bug-queues
,
Sep 27
webkit_layout_tests are marked experimental, removing sheriff label. Yunjia, please have a look at the flake or help assign a more suitable owner.
,
Jan 16
(6 days ago)
,
Jan 17
(5 days ago)
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pbos@chromium.org
, Sep 25Status: Assigned (was: Untriaged)