Bug 295738

Summary: [ macOS wk2 arm64 ] http/tests/images/gif-progressive-load.html is a flakey image failure
Product: WebKit Reporter: Bryan Medina <bmedina2>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: jbedard, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Image diffs none

Bryan Medina
Reported 2025-07-10 13:54:47 PDT
http/tests/images/gif-progressive-load.html is a flakey image failure occurring on macOS wk2 apple silicon HISTORY: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fimages%2Fgif-progressive-load.html IMAGE DIFF URL: https://build.webkit.org/results/Apple-Sequoia-Debug-AppleSilicon-WK2-Tests/297199@main%20(1848)/http/tests/images/gif-progressive-load-diffs.html Image diffs will be attached to bug, it appears to be off by 7.52%, images are supposed to appear on screen such as buildings, but nothing appears
Attachments
Image diffs (203.25 KB, application/zip)
2025-07-10 13:56 PDT, Bryan Medina
no flags
Radar WebKit Bug Importer
Comment 1 2025-07-10 13:55:15 PDT
Bryan Medina
Comment 2 2025-07-10 13:56:28 PDT
Created attachment 475870 [details] Image diffs
EWS
Comment 3 2025-07-10 14:35:06 PDT
Test gardening commit 297217@main (e6680620f5c4): <https://commits.webkit.org/297217@main> Reviewed commits have been landed. Closing PR #47846 and removing active labels.
Bryan Medina
Comment 4 2025-07-10 14:37:56 PDT
I was able to reproduce the image failure locally on macOS Seqouia Release ToT running the command: run-webkit-tests http/tests/images/gif-progressive-load.html --iterations=250 -f --force
Alexey Proskuryakov
Comment 5 2025-07-10 14:58:11 PDT
The actual image is blank.
EWS
Comment 6 2025-07-10 16:22:25 PDT
Test gardening commit 297228@main (59a732850947): <https://commits.webkit.org/297228@main> Reviewed commits have been landed. Closing PR #47859 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.