<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 - [GTK][Threaded Compositor] Several more flaky tests"
   href="https://bugs.webkit.org/show_bug.cgi?id=161688">161688</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[GTK][Threaded Compositor] Several more flaky tests
          </td>
        </tr>

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

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

        <tr>
          <th>Version</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux
          </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>WebKit Gtk
          </td>
        </tr>

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

        <tr>
          <th>Reporter</th>
          <td>mcatanzaro&#64;igalia.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>bugs-noreply&#64;webkitgtk.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Since we enabled threaded compositor, we now have a bunch of tests that occasionally pass when they usually fail. In build #18023 we have 84 unexpected passes, for example; that never happened before threaded compositor. What's interesting is these tests either always pass or always fail in a particular run of run-webkit-tests; they are clearly flaky, but they don't contribute to the flakiness count.

Carlos Garcia suggests in <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - [GTK][Threaded Compositor] Several flaky tests"
   href="show_bug.cgi?id=161242">bug #161242</a>#c20:

<span class="quote">&gt; I have theory, though. When they
&gt; unexpectedly pass, they don't actually pass, we just fail to render both the
&gt; actual and expected files in the same way (for example a fully white image
&gt; in both cases). That's a problem of the reftests. So, more interesting to
&gt; see what's failing, which can be also reproduced locally more easily, would
&gt; be to see what we render when they pass.</span ></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>