Bug 207971

Summary: [ Mac ] css3/selectors3/xml/css3-modsel-d1.xml is flaky failing.
Product: WebKit Reporter: Jason Lawrence <Lawrence.j>
Component: XMLAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: simon.fraser, webkit-bot-watchers-bugzilla, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Mac   
OS: macOS 10.14   

Jason Lawrence
Reported 2020-02-19 15:35:42 PST
css3/selectors3/xml/css3-modsel-d1.xml Description: This test is flaky failing on Mac throughout the visible history, the oldest failure I see is on r251443. The oldest failure that I'm able to recover a diff from is r254746, it's exactly the same. History: https://results.webkit.org/?suite=layout-tests&test=css3%2Fselectors3%2Fxml%2Fcss3-modsel-d1.xml&flavor=wk2&flavor=wk1&style=release&style=debug&platform=mac&limit=50000 Diff: --- /Volumes/Data/slave/catalina-release-tests-wk1/build/layout-test-results/css3/selectors3/xml/css3-modsel-d1-expected.txt +++ /Volumes/Data/slave/catalina-release-tests-wk1/build/layout-test-results/css3/selectors3/xml/css3-modsel-d1-actual.txt @@ -1,9 +1,11 @@ layer at (0,0) size 800x600 RenderView at (0,0) size 800x600 -layer at (0,0) size 800x82 - RenderBlock {test} at (0,0) size 800x82 - RenderBlock {div} at (0,16) size 800x66 +layer at (0,0) size 800x100 + RenderBlock {test} at (0,0) size 800x100 + RenderBlock {div} at (0,16) size 800x84 RenderBlock {p} at (0,0) size 800x18 RenderText {#text} at (0,0) size 225x18 text run at (0,0) width 225: "The following bar should be green." - RenderBlock {div} at (0,34) size 800x32 [bgcolor=#FF0000] + RenderBlock {div} at (0,34) size 800x50 [bgcolor=#00FF00] + RenderText {#text} at (16,16) size 166x18 + text run at (16,16) width 166: "This line should be green."
Attachments
Radar WebKit Bug Importer
Comment 1 2020-02-19 15:36:14 PST
Jason Lawrence
Comment 2 2020-02-19 15:46:09 PST
I have marked this test as failing while this issue is investigated. https://trac.webkit.org/changeset/256987/webkit
Alexey Proskuryakov
Comment 3 2020-02-19 22:33:42 PST
Clearly a bad test with its 100 ms timeout. Since it's an imported one, perhaps we should just delete it? Or fix because upstream won't ever be updated?
Note You need to log in before you can comment on or make changes to this bug.