<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>187931</bug_id>
          
          <creation_ts>2018-07-23 15:53:26 -0700</creation_ts>
          <short_desc>REGRESSION: Multiple svg layout tests have become flaky timeouts</short_desc>
          <delta_ts>2018-08-06 08:57:25 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Animations</component>
          <version>Other</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords>InRadar</keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Ryan Haddad">ryanhaddad</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>dino</cc>
    
    <cc>realdawei</cc>
    
    <cc>simon.fraser</cc>
    
    <cc>tsavell</cc>
    
    <cc>webkit-bug-importer</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1444447</commentid>
    <comment_count>0</comment_count>
    <who name="Ryan Haddad">ryanhaddad</who>
    <bug_when>2018-07-23 15:53:26 -0700</bug_when>
    <thetext>Multiple svg layout tests have timed out at least once on macOS bots in the past 2 days:

svg/animations/animations-paused-in-background-page-iframe.html
svg/animations/deferred-insertion.html
svg/animations/change-target-while-animating-SVG-property.html
svg/animations/multiple-animations-ending.html
svg/animations/smil-leak-dynamically-added-element-instances.svg
svg/animations/svglength-additive-from-by-4.html
svg/animations/svgenum-animation-10.html
svg/animations/svg-two-animate-elements-crash.svg
svg/animations/svgenum-animation-3.html
svg/animations/single-values-animation.html
svg/animations/svgangle-animation-grad-to-rad.html
svg/animations/force-use-shadow-tree-recreation-while-animating.html
svg/animations/non-additive-type-by-animation.html

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&amp;tests=svg%2Fanimations%2F</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1444450</commentid>
    <comment_count>1</comment_count>
    <who name="Ryan Haddad">ryanhaddad</who>
    <bug_when>2018-07-23 15:58:17 -0700</bug_when>
    <thetext>Perhaps related, I noticed that svg/zoom/page/zoom-svg-through-object-with-percentage-size.xhtml was reported as missing expected results on this test run, but the test isn&apos;t new and does indeed have an iOS expected.txt file:

https://build.webkit.org/results/Apple%20iOS%2011%20Simulator%20Release%20WK2%20(Tests)/r234110%20(6375)/results.html</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1444451</commentid>
    <comment_count>2</comment_count>
    <who name="Ryan Haddad">ryanhaddad</who>
    <bug_when>2018-07-23 15:59:57 -0700</bug_when>
    <thetext>One of the earliest timeouts I see was with svg/animations/end-event-syncbase.svg, which blames https://trac.webkit.org/log/?verbose=on&amp;rev=234078&amp;stop_rev=234077

https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20WK2%20(Tests)/builds/5757</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1444455</commentid>
    <comment_count>3</comment_count>
    <who name="Ryan Haddad">ryanhaddad</who>
    <bug_when>2018-07-23 16:00:54 -0700</bug_when>
    <thetext>This change was related to animations:
&quot;Remove completed animations from GraphicsLayer, thus avoiding excessive backing store allocation&quot;
https://trac.webkit.org/changeset/234073/webkit</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1444466</commentid>
    <comment_count>4</comment_count>
    <who name="Simon Fraser (smfr)">simon.fraser</who>
    <bug_when>2018-07-23 16:13:21 -0700</bug_when>
    <thetext>(In reply to Ryan Haddad from comment #3)
&gt; This change was related to animations:
&gt; &quot;Remove completed animations from GraphicsLayer, thus avoiding excessive
&gt; backing store allocation&quot;
&gt; https://trac.webkit.org/changeset/234073/webkit

That shouldn&apos;t have any impact on SVG animations.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1445597</commentid>
    <comment_count>5</comment_count>
    <who name="Radar WebKit Bug Importer">webkit-bug-importer</who>
    <bug_when>2018-07-26 17:08:36 -0700</bug_when>
    <thetext>&lt;rdar://problem/42643928&gt;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1448128</commentid>
    <comment_count>6</comment_count>
    <who name="Truitt Savell">tsavell</who>
    <bug_when>2018-08-06 08:57:25 -0700</bug_when>
    <thetext>After further testing and help from Johnathan, I found that running the directories storage/indexeddb/modern/ and svg/ in succession with one test runner reproduced the issue. I bisected the storage/indexeddb/modern/ directory down to find that storage/indexeddb/modern/opendatabase-after-storage-crash.html  is the casue of the flakey timouts. If you run this test in front tof the svg/ directory there is a chance of a timout occuring. 

Test Command Line:
Run-webkit-tests --root testbuild-234505 storage/indexeddb/modern/opendatabase-after-storage-crash.html   svg/ --child-processes 1 -v

I then marked the test as skip locally and ran both directories again 10 times with no timouts occuring. 

Next steps are to mark the test as skip for now and work to find a proper solution.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>