<?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>210790</bug_id>
          
          <creation_ts>2020-04-21 04:33:15 -0700</creation_ts>
          <short_desc>[ARMv7] run stress/check-stack-overflow-before-value-profiling-arguments.js</short_desc>
          <delta_ts>2020-06-19 07:05:44 -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>JavaScriptCore</component>
          <version>WebKit Nightly Build</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></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>213373</dependson>
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Paulo Matos">pmatos</reporter>
          <assigned_to name="Paulo Matos">pmatos</assigned_to>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1643843</commentid>
    <comment_count>0</comment_count>
    <who name="Paulo Matos">pmatos</who>
    <bug_when>2020-04-21 04:33:15 -0700</bug_when>
    <thetext>In 210720 we skipped test stress/check-stack-overflow-before-value-profiling-arguments.js on ARMv7 which was failing on EWS.

This failure is due to a specific condition that arose recently where the test is scheduled in the same rpi3 together with other memory-hungry tests that make this test crash. The same doesn&apos;t happen in the post-commit bot which happily passes the test.

It&apos;s a shame to skip a test that passes simply because it happens to be scheduled with other memory hungry tests. We should possibly have a way to say that the test should not be scheduled on the remote with other tests so it runs standalone.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>