Bug 254289
| Summary: | REGRESSION(259811@main-259818@main): [ iOS Debug ] 4X TestWebKitAPI.AppPrivacyReport (API-Tests) are failing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Robert Jenner <jenner> |
| Component: | Tools / Tests | Assignee: | Ryan Haddad <ryanhaddad> |
| Status: | REOPENED | ||
| Severity: | Normal | CC: | ap, bfulgham, webkit-bot-watchers-bugzilla, webkit-bug-importer, wenson_hsieh, wilander |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Robert Jenner
The following 4X TestWebKitAPI.AppPrivacyReport (API-Tests) are constant timeouts on iOS Debug:
TestWebKitAPI.AppPrivacyReport.RestoreFromInteractionStateIsAppInitiated
TestWebKitAPI.AppPrivacyReport.RestoreFromInteractionStateIsNonAppInitiated
TestWebKitAPI.AppPrivacyReport.RestoreFromSessionStateIsAppInitiated
TestWebKitAPI.AppPrivacyReport.RestoreFromSessionStateIsNonAppInitiated
HISTORY:
https://results.webkit.org/?suite=api-tests&suite=api-tests&suite=api-tests&suite=api-tests&test=TestWebKitAPI.AppPrivacyReport.RestoreFromInteractionStateIsAppInitiated&test=TestWebKitAPI.AppPrivacyReport.RestoreFromInteractionStateIsNonAppInitiated&test=TestWebKitAPI.AppPrivacyReport.RestoreFromSessionStateIsAppInitiated&test=TestWebKitAPI.AppPrivacyReport.RestoreFromSessionStateIsNonAppInitiated
These tests appeared to be flaky timeouts, but switched to constant timeouts for debug iOS only between 259811@main and 259818@main
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/107077600>
Robert Jenner
The other interesting thing about these tests is that they do appear to be consistently timing out on EWS observed here:
https://ews-build.webkit.org/#/builders/13
However, they do not appear to be timing out on release in OpenSource/Post-commit testing.
Robert Jenner
I was able to reproduce the timeouts at iOS 16 Debug ToT running the tests as follows:
run-api-tests --ios-simulator <test_goes_here> --debug
I will now attempt to bisect and uncover the regression point.
Alexey Proskuryakov
This is marked RESOLVED/FIXED. but I see a false positive on EWS from these tests: https://ews-build.webkit.org/#/builders/13/builds/467
Ryan Haddad
Reopening.
Ryan Haddad
rdar://107268120
Ryan Haddad
Pull request: https://github.com/WebKit/WebKit/pull/12007
EWS
Test gardening commit 262152@main (1fa0bf2759a8): <https://commits.webkit.org/262152@main>
Reviewed commits have been landed. Closing PR #12007 and removing active labels.
Alexey Proskuryakov
Renaming to not say "constant timeouts", as the tests were flaky on EWS, causing false positives. But they definitely were 100% timing out in post commit.
EWS
Test gardening commit 259548.509@safari-7615-branch (96be2e666d51): <https://commits.webkit.org/259548.509@safari-7615-branch>
Reviewed commits have been landed. Closing PR #504 and removing active labels.
Ryan Haddad
Pull request: https://github.com/WebKit/WebKit/pull/13600
Ryan Haddad
(In reply to Ryan Haddad from comment #11)
> Pull request: https://github.com/WebKit/WebKit/pull/13600
^ this was to unskip the tests to see how they fared, they are still timing out.