No subject

Tue May 3 15:05:30 PDT 2016

Just a quick statistic:
- AArch64, ARMv7 Thumb2, ARMv7 Traditional and GTK ARM bots
now run 36.000 tests instead of 20.000, the extra 16.000 tests
don't add anything for testing, they are simply duplicated tests.
- runtime on AArch64 bot: 73 mins -> 112 mins
- runtime on ARMv7 Thumb2 bot: 109 mins -> 168 mins
- runtime on ARMv7 ARM traditional bot: 186 mins -> 260 mins
- runtime on ARM GTK (Thumb2) bot: 48 mins -> 76 mins

"So, maybe rather than preserving this broken feature, we should create
something that (a) acknowledges the fact that the FTL is the default on those
platforms that support it and (b) avoids running no-ftl tests on precisely those
platforms that don't have FTL."

OK, so when do you plan to fix this completely broken jsc-stress-tests
script not to run extra tests on 32-bit platforms which won't have
FTL JIT ever in the future? It's not fair to increase the test runtime
on 32-bit platforms just to paint your extra slow debug bot green.

----

Apple Internal ARM bots are now timing out after 2 hours.

-- 
You are receiving this mail because:
You are the assignee for the bug.
--1469141730.c112B8.19099
Date: Thu, 21 Jul 2016 15:55:30 -0700
MIME-Version: 1.0
Content-Type: text/html

<html>
    <head>
      <base href="https://bugs.webkit.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - REGRESSION(r203440): JSC Testing time on ARM devices increased by 50%"
   href="https://bugs.webkit.org/show_bug.cgi?id=160058">160058</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>REGRESSION(r203440): JSC Testing time on ARM devices increased by 50%
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>WebKit Nightly Build
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>JavaScriptCore
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned&#64;lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>msaboff&#64;apple.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>From <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - The default testing mode should not involve disabling the FTL JIT"
   href="show_bug.cgi?id=159929#c13">https://bugs.webkit.org/show_bug.cgi?id=159929#c13</a>:
Just a quick statistic:
- AArch64, ARMv7 Thumb2, ARMv7 Traditional and GTK ARM bots
now run 36.000 tests instead of 20.000, the extra 16.000 tests
don't add anything for testing, they are simply duplicated tests.
- runtime on AArch64 bot: 73 mins -&gt; 112 mins
- runtime on ARMv7 Thumb2 bot: 109 mins -&gt; 168 mins
- runtime on ARMv7 ARM traditional bot: 186 mins -&gt; 260 mins
- runtime on ARM GTK (Thumb2) bot: 48 mins -&gt; 76 mins

&quot;So, maybe rather than preserving this broken feature, we should create
something that (a) acknowledges the fact that the FTL is the default on those
platforms that support it and (b) avoids running no-ftl tests on precisely those
platforms that don't have FTL.&quot;

OK, so when do you plan to fix this completely broken jsc-stress-tests
script not to run extra tests on 32-bit platforms which won't have
FTL JIT ever in the future? It's not fair to increase the test runtime
on 32-bit platforms just to paint your extra slow debug bot green.

----

Apple Internal ARM bots are now timing out after 2 hours.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>
--1469141730.c112B8.19099--