<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Brent<br>
<br>
thank you very much for this effort!<br>
<br>
Thomas<br>
<br>
<div class="moz-cite-prefix">Am 21.02.2015 um 03:02 schrieb Brent
Fulgham:<br>
</div>
<blockquote
cite="mid:2815B1E3-EB06-4B4B-8899-A69EA4B0AB5B@apple.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi Everyone,
<div class=""><br class="">
</div>
<div class="">Over the past few weeks I’ve spent a considerable
amount of time reviewing and correcting a number of problems
with the Windows testing infrastructure.</div>
<div class=""><br class="">
</div>
<div class="">We were skipping thousands of tests, including
Accessibility, http tests, and large sections of forms, css, and
svg tests. Some tests were skipped because features were
supposedly incomplete, but in the years since the skip entry was
added to the file, the work had been completed and feature
worked perfectly well. Some tests were skipped simply because
feature flags had never been enabled on Windows.</div>
<div class=""><br class="">
</div>
<div class="">Happily, all of this is in the past. Now that this
work is complete, we have much more test coverage of many areas
of WebKit that had been previously ignored on this platform.</div>
<div class=""><br class="">
</div>
<div class="">1. We are now using native Windows Apache to run our
HTTP tests, and have been doing so for the past couple of weeks.
This seems to be quite stable, and is allowing us to make sure
SSL and other important features work properly on Windows.</div>
<div class="">2. Accessibility tests are back up and running.</div>
<div class="">3. Thanks to Ossy, we now run all JSC stress tests
on Windows.</div>
<div class="">4. Nearly all other tests are now running, with a
few notable exceptions below.</div>
<div class="">5. I have switched to running Windows tests in a
single process, because I found that running in parallel
introduced inconsistent results. (See <<a
moz-do-not-send="true"
href="https://bugs.webkit.org/show_bug.cgi?id=140914" class="">https://bugs.webkit.org/show_bug.cgi?id=140914</a>>).</div>
<div class=""><br class="">
</div>
<div class="">So now that I’ve completed this task, PLEASE help
keep the Windows bots green! :-)</div>
<div class=""><br class="">
</div>
<div class="">If you are at all interested in the various Windows
ports, and are looking for something to do, there are a number
of bugs I’ve filed that could use some attention:</div>
<div class=""><br class="">
</div>
<div class="">1. For some reason, running layout tests in parallel
introduces inconsistent behavior and spurious failures. There
must be some kind of cross-talk between the different shards.
<<a moz-do-not-send="true"
href="https://bugs.webkit.org/show_bug.cgi?id=140914" class="">https://bugs.webkit.org/show_bug.cgi?id=140914</a>>.</div>
<div class="">2. There are a number of debug assertions firing
that cause Debug test runs to exit early. (see <<a
moz-do-not-send="true"
href="https://bugs.webkit.org/show_bug.cgi?id=140517" class="">https://bugs.webkit.org/show_bug.cgi?id=140517</a>>, </div>
<div class="">3. Something weird is going on with the page cache.
<<a moz-do-not-send="true"
href="https://bugs.webkit.org/show_bug.cgi?id=140190" class="">https://bugs.webkit.org/show_bug.cgi?id=140190</a>, <a
moz-do-not-send="true"
href="https://bugs.webkit.org/show_bug.cgi?id=140871" class="">https://bugs.webkit.org/show_bug.cgi?id=140871</a>></div>
<div class="">4. Accessibility tests have a number of problems:</div>
<div class="">(a) Several Accessibility tests fail in debug mode
because they assert that they are accessing text iterators
before layout is complete. The comment with this assertion
indicates that this can cause crashes and instability. <<a
moz-do-not-send="true"
href="https://bugs.webkit.org/show_bug.cgi?id=140867" class="">https://bugs.webkit.org/show_bug.cgi?id=140867</a>></div>
<div class="">(b) Some accessibility tests are very flaky with
regard to digging down into the DOM. Test will pass one run,
fail the next. <<a moz-do-not-send="true"
href="https://bugs.webkit.org/show_bug.cgi?id=140798" class="">https://bugs.webkit.org/show_bug.cgi?id=140798</a>></div>
<div class=""><br class="">
</div>
<div class="">Feel free to contact me any time if you want to
tackle any of these problems!</div>
<div class=""><br class="">
</div>
<div class="">Otherwise, please just help keep the Windows bots
green. I don’t want to have to go through all of this again! :-)</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class=""><br class="">
</div>
<div class="">-Brent</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
webkit-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a>
<a class="moz-txt-link-freetext" href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>