<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 04/21/2016 10:13 AM, Michail Chernov
wrote:<br>
</div>
<blockquote cite="mid:57190A3C.2010207@oracle.com" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
Hi,<br>
<br>
<br>
<blockquote cite="mid:5718A1A2.1080703@oracle.com" type="cite">
<blockquote cite="mid:5717FF06.6070405@oracle.com" type="cite">
<blockquote cite="mid:5717B411.5000705@oracle.com" type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
HI Jon,<br>
<br>
This is the way to remove new unified logging options, like
-Xlog:all=trace or -Xlog:gc*=trace. Tests define -Xlog:...
inside for checking,</blockquote>
Sorry, but I still don't understand. "Tests define -Xlog:..."
means that the tests<br>
have built into them unified logging style flags?<br>
</blockquote>
<br>
Michail used not proper wording "will conflict". The flags of
the tests and possible external -Xlog flags will not conflict,
but the test might fail, if external options turn more logging
on.<br>
The fix protects the test from extra logging.<br>
<br>
Michail, the fix looks good to me.<br>
<br>
</blockquote>
<br>
Dima, thanks for your review. Your explanation describes reason of
this change correctly. External -Xlog* flags can make logging
level more detailed than tests wait for.<br>
</blockquote>
<br>
Thanks for the explanation. Changes look good.<br>
<br>
Jon<br>
<br>
<blockquote cite="mid:57190A3C.2010207@oracle.com" type="cite"> <br>
Thanks,<br>
Michail<br>
</blockquote>
<br>
</body>
</html>