Bug 207116 - [ iOS wk2 ] compositing/backing/page-scale-overlap-in-iframe.html failing.
Summary: [ iOS wk2 ] compositing/backing/page-scale-overlap-in-iframe.html failing.
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-02-03 08:07 PST by Jason Lawrence
Modified: 2020-04-08 22:50 PDT (History)
4 users (show)

See Also:

Attachments
Update Test Expectations (1.46 KB, patch)
2020-02-03 08:16 PST, Jason Lawrence 		no flags Details | Formatted Diff | Diff
Update Test Expectations (4.60 KB, patch)
2020-02-03 13:10 PST, Jason Lawrence 		no flags Details | Formatted Diff | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Lawrence 2020-02-03 08:07:14 PST 
compositing/backing/page-scale-overlap-in-iframe.html

Description:
This test is failing on iOS wk2 debug and iPad and flaky failing on other iOS wk2 devices. 

History:
https://results.webkit.org/?suite=layout-tests&test=compositing%2Fbacking%2Fpage-scale-overlap-in-iframe.html&limit=50000&platform=ios

Diff:
--- /Volumes/Data/slave/ipados-simulator-13-debug-tests-wk2/build/layout-test-results/compositing/backing/page-scale-overlap-in-iframe-expected.txt
+++ /Volumes/Data/slave/ipados-simulator-13-debug-tests-wk2/build/layout-test-results/compositing/backing/page-scale-overlap-in-iframe-actual.txt
@@ -1,11 +1,11 @@
 
 (GraphicsLayer
   (anchor 0.00 0.00)
-  (bounds 800.00 1370.00)
+  (bounds 800.00 1046.00)
   (backingStoreAttached 1)
   (children 1
     (GraphicsLayer
-      (bounds 800.00 1370.00)
+      (bounds 800.00 1046.00)
       (contentsOpaque 1)
       (backingStoreAttached 1)
       (children 1
Comment 1 Radar WebKit Bug Importer 2020-02-03 08:07:42 PST 
<rdar://problem/59110819>
Comment 2 Jason Lawrence 2020-02-03 08:16:06 PST 
Created attachment 389510 [details]
Update Test Expectations
Comment 3 Truitt Savell 2020-02-03 08:23:51 PST 
Comment on attachment 389510 [details]
Update Test Expectations

Clearing flags on attachment: 389510

Committed r255561: <https://trac.webkit.org/changeset/255561>
Comment 4 Simon Fraser (smfr) 2020-02-03 10:31:33 PST 
I only see iPad failures. Why was it marked as failing across all devices?
Comment 5 Truitt Savell 2020-02-03 10:37:24 PST 
(In reply to Simon Fraser (smfr) from comment #4)
> I only see iPad failures. Why was it marked as failing across all devices?

fixed that in https://trac.webkit.org/changeset/255573/webkit
Comment 6 Jason Lawrence 2020-02-03 13:10:58 PST 
Created attachment 389547 [details]
Update Test Expectations
Comment 7 Truitt Savell 2020-02-03 13:12:46 PST 
Comment on attachment 389547 [details]
Update Test Expectations

Clearing flags on attachment: 389547

Committed r255583: <https://trac.webkit.org/changeset/255583>
Comment 8 Alexey Proskuryakov 2020-02-03 23:30:31 PST 
> I only see iPad failures. Why was it marked as failing across all devices?

This test was initially failing on iPhone too (with a different diff). Very surprisingly, but also very clearly, it stopped to fail on iPhone with r255334.
Comment 9 Alexey Proskuryakov 2020-02-03 23:39:57 PST 
Sorry, getting too tired. The iPhone progression was r255332 of course.
Comment 10 Ryan Haddad 2020-04-08 22:50:03 PDT 
The test is passing. Resolving this bug.