NEW297240
REGRESSION(297118@main): [ iPadOS ] http/tests/site-isolation/edge-sampling-commit-root-frame-load.html is a constant text failure
https://bugs.webkit.org/show_bug.cgi?id=297240
Summary REGRESSION(297118@main): [ iPadOS ] http/tests/site-isolation/edge-sampling-c...
Bryan Medina
Reported 2025-08-11 14:07:53 PDT
http/tests/site-isolation/edge-sampling-commit-root-frame-load.html is a constant text failure on iPadOS. HISTORY: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fsite-isolation%2Fedge-sampling-commit-root-frame-load.html TEXT DIFF: --- /Volumes/Data/worker/Apple-iPadOS-18-Simulator-Release-WK2-Tests/build/layout-test-results/http/tests/site-isolation/edge-sampling-commit-root-frame-load-expected.txt +++ /Volumes/Data/worker/Apple-iPadOS-18-Simulator-Release-WK2-Tests/build/layout-test-results/http/tests/site-isolation/edge-sampling-commit-root-frame-load-actual.txt @@ -1,3 +1,3 @@ -ALERT: PASS +ALERT: FAIL null TEXT DIFF URL: https://build.webkit.org/results/Apple-iPadOS-18-Simulator-Release-WK2-Tests/298441@main%20(1690)/http/tests/site-isolation/edge-sampling-commit-root-frame-load-diff.txt
Attachments
Radar WebKit Bug Importer
Comment 1 2025-08-11 14:08:09 PDT
EWS
Comment 2 2025-08-11 14:27:01 PDT
Test gardening commit 298528@main (9f3f0bed6126): <https://commits.webkit.org/298528@main> Reviewed commits have been landed. Closing PR #49237 and removing active labels.
Bryan Medina
Comment 3 2025-08-11 14:33:20 PDT
I was able to reproduce the text failure locally on my device running iOS 18 simulator Debug ToT using the following command: run-webkit-tests http/tests/site-isolation/edge-sampling-commit-root-frame-load.html --iPad-simulator
Bryan Medina
Comment 4 2025-08-11 14:52:00 PDT
Referring to the history, it is shown that the tests were failing somewhere between 297117@main and 297127@main. Using reproduction steps above, I found that the tests were passing at 297117@main, but failed at 297118@main. At this time, I believe that the regression point is 297118@main.
Note You need to log in before you can comment on or make changes to this bug.