ietestcenter/css3/grid/grid-column-003.htm is flaky on WebKit Linux Leak |
|||||
Issue descriptionhttps://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=ietestcenter%2Fcss3%2Fgrid%2Fgrid-column-003.htm&testType=webkit_tests Tentatively assigning to rego@igalia.com. Could you please route to the correct person?
,
Jun 27 2016
I don't know what's going on, we'd need to investigate it: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20Leak/builds/20563
,
Jul 8 2016
@dgozman please could you tell me how to reproduce the Leak bot configuration? Where can I find the GN/GYP variables it uses? Thanks! The test runs just fine in a regular build.
,
Jan 10 2017
Coming back to this, it's a very simple test so it's really strange it's the only one from all the Grid Layout tests that is leaking on Linux. It's just a 2x2 grid container with 2 items in 1x1 cell. As we cannot reproduce it and we didn't get any feedback about how to do it, would be ok to remove it from TestExpectations and see if the issue appears again?
,
Dec 5 2017
Yes, let's give it a try.
,
Dec 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0935af5345e6d007f7bd2bee7a7cc06d8f1f627b commit 0935af5345e6d007f7bd2bee7a7cc06d8f1f627b Author: Manuel Rego Casasnovas <rego@igalia.com> Date: Wed Dec 06 18:36:12 2017 [css-grid] Enable ietestcenter/css3/grid/grid-column-003.htm again Remove ietestcenter/css3/grid/grid-column-003.htm from TestExpectations as we didn't manage to reproduce the leak. Let's see if the bots detect it again or it was already fixed. BUG= 622915 Change-Id: Ibd03c81d5074c6c73cf78abba3ef0abec07aea36 Reviewed-on: https://chromium-review.googlesource.com/809206 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#522144} [modify] https://crrev.com/0935af5345e6d007f7bd2bee7a7cc06d8f1f627b/third_party/WebKit/LayoutTests/TestExpectations
,
Dec 11 2017
Closing this at this point that we've re-enabled the test as we were not able to reproduce it. Let's see if the issue appears again or not. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Jun 24 2016