Hi Kamil,<div><br></div><div>I&#39;d like to nominate the following, but I want some discussions from the owners to see if there&#39;s something we could do first:</div><div><br></div><div>1) kernel32:pipe has always been pretty random to me, due to race conditions in NPFS, I believe.</div>

<div>2) urlmon:url is wildly random/erratic, I believe due to ws2_32:sock</div><div><br clear="all">Best regards,<br>Alex Ionescu<br>
<br><br><div class="gmail_quote">On Sat, Feb 11, 2012 at 4:28 PM, Kamil Hornicek <span dir="ltr">&lt;<a href="mailto:kamil.hornicek@reactos.org">kamil.hornicek@reactos.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hi,<br>
as requested I added a blacklisting ability to testman. The purpose of this is to have some meaningful comparison between test runs without completely disabling randomly behaving test sets. This means that blacklisted test are still being run, logged and included in the Totals summary. They won&#39;t affect the newly added &quot;nonblacklisted summary&quot; only. The last thing needed before we can actually benefit from this is to go through the tests, find those that give random results and either fix them or add them to the blacklist. Please use this wiki page <a href="http://www.reactos.org/wiki/Testman_blacklist" target="_blank">http://www.reactos.org/wiki/<u></u>Testman_blacklist</a> to forge the list. Anyone with web repo commit access (that includes me) can then update the config itself.<br>


<br>
WBR,<br>
Kamil<br>
<br>
______________________________<u></u>_________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org" target="_blank">Ros-dev@reactos.org</a><br>
<a href="http://www.reactos.org/mailman/listinfo/ros-dev" target="_blank">http://www.reactos.org/<u></u>mailman/listinfo/ros-dev</a><br>
</blockquote></div><br></div>