Bug 297614
| Summary: | [ macOS Sequoia wk2 Debug x86_64 ] fast/canvas/hdr/float16-canvas-imagedata.html is a constant timeout | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Bryan Medina <bmedina2> |
| Component: | Canvas | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | g_squelart, mwyrzykowski, sabouhallawa, webkit-bot-watchers-bugzilla, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 297649 | ||
Bryan Medina
fast/canvas/hdr/float16-canvas-imagedata.html
is a constant timeout on macOS wk2 Sequoia Debug on x86_64.
HISTORY:
https://results.webkit.org/?suite=layout-tests&test=fast%2Fcanvas%2Fhdr%2Ffloat16-canvas-imagedata.html&limit=50000&recent=false
TEXT DIFF:
*Test timed out before a diff could be reproduced
TEXT DIFF URL:
https://build.webkit.org/results/Apple-Sequoia-Debug-WK2-Tests/298886@main%20(1955)/results.html
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/158709235>
Bryan Medina
I was unable to reproduce the timeout locally on my device running macOS Sequoia Debug x86_64 using the following command:
run-webkit-tests fast/canvas/hdr/float16-canvas-imagedata.html --iterations=100 --debug
EWS
Test gardening commit 298917@main (1b579a6884a6): <https://commits.webkit.org/298917@main>
Reviewed commits have been landed. Closing PR #49613 and removing active labels.
Alexey Proskuryakov
Looks like this already got fixed through a follow-up commit on bug 297649, instead of using this bug.
Alexey Proskuryakov
Actually misread the history, not a follow-up, just a second bug filed.
*** This bug has been marked as a duplicate of bug 297649 ***
Gerald Squelart
This bug here is just "test gardening", it removed the timeout by skipping the test.
Bug 297649 contains the proper fix after that, it reversed the commit here to re-enable the test, and improved the test to avoid timeouts.
So I'm not sure it qualifies as duplicate?
Should I have linked my fix to this bug here instead of creating a separate one?