Bug 257231

Summary: [ iPhone XS+ ] TestWebKitAPI.AnimatedResize.ResizeWithContentHiddenWhileScrolling is a constant failure
Product: WebKit Reporter: Robert Jenner <jenner>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: akeerthi, thorton, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=256662

Description Robert Jenner 2023-05-23 15:10:38 PDT
TestWebKitAPI.AnimatedResize.ResizeWithContentHiddenWhileScrolling

is a constant failure on iOS 16 on a simulated device that is an iPhone XS and higher. 

HISTORY:
https://results.webkit.org/?suite=api-tests&test=TestWebKitAPI.AnimatedResize.ResizeWithContentHiddenWhileScrolling

As you can see in the history, it currently passes. That's because our current simulator is set to iPhone SE (3rd gen) We would like to set it to iPhone 12 though, and in doing so this would show as a constant failure. 

STDIO FAILURE TEXT:
    TestWebKitAPI.AnimatedResize.ResizeWithContentHiddenWhileScrolling
        LEAK: 1 WebProcessPool

        /Volumes/Data/worker/trunk-sydneye-ios-simulator-debug-archive/build/OpenSource/Tools/TestWebKitAPI/Tests/WebKitCocoa/AnimatedResize.mm:508
        Expected equality of these values:
          innerHeight
            Which is: 153
          200
Comment 1 Radar WebKit Bug Importer 2023-05-23 15:11:32 PDT
<rdar://problem/109741178>
Comment 2 Robert Jenner 2023-05-23 15:12:30 PDT
This is very easy to reproduce on iOS 16 Debug ToT running the test as follows:

run-api-tests --iOS-simulator TestWebKitAPI.AnimatedResize.ResizeWithContentHiddenWhileScrolling

You will specifically need to boot an iPhone XS or higher simulator to get the failure. After you have chosen your booted simulator it will choose to run on that simulated device, and not the one that we have set for our testing.
Comment 3 Robert Jenner 2023-05-23 15:49:02 PDT

*** This bug has been marked as a duplicate of bug 257228 ***