<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 23, 2016 at 7:39 PM, Philip Race <span dir="ltr"><<a href="mailto:philip.race@oracle.com" target="_blank">philip.race@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
We have a PIT (pre-integration-testing process) but if<br>
that these clashes are presented only as an FYI and not<br>
an actual failure then SQE might not notice it. It may<br>
even get swallowed and not forwarded for human inspection<br>
by some layered tool on top.<br>
I don't actually know .. I am just speculating.</div></blockquote><div><br></div><div>I do know that the awt clash caused my jtreg command to exit with a non-zero return code, which causes my own little integration pipeline to come to a halt (as it should!). </div><div><br></div><div>So your PIT process should be checked to ensure that a jtreg regression cannot slip through.</div></div></div></div>