NEW 284954
New Test (263412@main): [ macOS wk1 ] imported/w3c/web-platform-tests/css/css-box/margin-trim/computed-margin-values/block-container-block-start-child-with-border.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=284954
Summary New Test (263412@main): [ macOS wk1 ] imported/w3c/web-platform-tests/css/css...
Karl Rackler
Reported 2024-12-19 07:36:49 PST
Description: imported/w3c/web-platform-tests/css/css-box/margin-trim/computed-margin-values/block-container-block-start-child-with-border.html The test was added at 263412@main and has been a flaky failure on macOS wk1 since then. This issue can be reproduced using command: run-webkit-tests --release --no-retry --force -1 --iterations=50 imported/w3c/web-platform-tests/css/css-box/margin-trim/computed-margin-values/block-container-block-start-child-with-border.html Result: Unexpected flakiness: text-only failures (1) imported/w3c/web-platform-tests/css/css-box/margin-trim/computed-margin-values/block-container-block-start-child-with-border.html [ Failure Pass ] History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fcss%2Fcss-box%2Fmargin-trim%2Fcomputed-margin-values%2Fblock-container-block-start-child-with-border.html&flavor=wk1&recent=false Diff: -PASS item 1 -PASS item 2 +FAIL item 1 assert_equals: +<item data-expected-margin-top="0" class="collapsed"> + <item data-expected-margin-top="0" class="collapsed"></item> + </item> +margin-top expected "0" but got "50" +FAIL item 2 assert_equals: +<item data-expected-margin-top="0" class="collapsed"></item> +margin-top expected "0" but got "50" PASS item 3 PASS item 4
Attachments
Radar WebKit Bug Importer
Comment 1 2024-12-19 07:38:22 PST
EWS
Comment 2 2024-12-19 07:45:16 PST
Test gardening commit 288089@main (ea534c6ac014): <https://commits.webkit.org/288089@main> Reviewed commits have been landed. Closing PR #38209 and removing active labels.
Sammy Gill
Comment 3 2024-12-19 14:31:54 PST
Sammy Gill
Comment 4 2024-12-19 14:44:08 PST
Note You need to log in before you can comment on or make changes to this bug.