NEW 241376
[ macOS wk1 ] imported/w3c/web-platform-tests/css/css-sizing/aspect-ratio/replaced-element-035.html is a flaky image failure
https://bugs.webkit.org/show_bug.cgi?id=241376
Summary [ macOS wk1 ] imported/w3c/web-platform-tests/css/css-sizing/aspect-ratio/rep...
Karl Rackler
Reported 2022-06-07 11:08:27 PDT
Description: imported/w3c/web-platform-tests/css/css-sizing/aspect-ratio/replaced-element-035.html The first failure that I saw on the dashboard was on 4/15/2022 at 249678@main, but this does not appear relevant to causing this issue. This test has been flaky for its entire history on the dashboard. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fcss%2Fcss-sizing%2Faspect-ratio%2Freplaced-element-035.html&limit=50000&flavor=wk1 Image Diff: https://build.webkit.org/results/Apple-Monterey-Release-WK1-Tests/251353@main%20(3784)/imported/w3c/web-platform-tests/css/css-sizing/aspect-ratio/replaced-element-035-diffs.html
Attachments
Radar WebKit Bug Importer
Comment 1 2022-06-07 11:10:33 PDT
Karl Rackler
Comment 2 2022-06-07 11:17:43 PDT
I have marked this test as a flaky image failure while this issue is investigated.
Karl Rackler
Comment 3 2022-06-07 11:18:42 PDT
EWS
Comment 4 2022-06-07 11:22:26 PDT
Test gardening commit r295358 (251367@main): <https://commits.webkit.org/251367@main> Reviewed commits have been landed. Closing PR #1353 and removing active labels.
Karl Rackler
Comment 5 2022-06-07 11:42:21 PDT
REPRODUCTION STEPS I can reproduce this on ToT ( r295346 ) Command: run-webkit-tests -1 --exit-after-n-failures 1 --exit-after-n-crashes-or-timeouts 1 --iterations 50 -f --no-retry imported/w3c/web-platform-tests/css/css-sizing/aspect-ratio/replaced-element-035.html Result: Regressions: Unexpected image-only failures (1) imported/w3c/web-platform-tests/css/css-sizing/aspect-ratio/replaced-element-035.html [ ImageOnlyFailure ]
Ryan Haddad
Comment 6 2022-06-08 15:30:30 PDT
This test was imported on April 15 with https://commits.webkit.org/249676@main, so it has probably been flaky from the start.
Note You need to log in before you can comment on or make changes to this bug.