<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 02/10/2025 18:09, Pavel Rappo wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAChcVu=Ob+3kEOmRXbi7UrnGkmOdtq-5CqPee+Z7cURdCfQ26w@mail.gmail.com">
<pre wrap="" class="moz-quote-pre">Hello,
This has been probably asked multiple times, but I cannot quickly find
anything. I'm running a set of tests as follows:
make test TEST="test/jdk/java/time/"
If a test fails, sometimes I get this output:
...
Output overflow:
JT Harness has limited the test output to the text
at the beginning and the end, so that you can see how the
test began, and how it completed.
If you need to see more of the output from the test,
set the system property javatest.maxOutputSize to a higher
value. The current value is 100000
...
</pre>
</blockquote>
At some point I think we need to think again about having <span style="white-space: pre-wrap">maxOutputSize set to a very large value in the TEST.ROOT for least the test/jdk test. There are many parameterized tests that result in lot of output but it very important output for diagnosing failures, even the "STARTED" and "SUCCESSFUL" messages for JUnit tests as they give you the execution time for specific tests when trying to diagnose timeouts and slow downs. Right now, we have TEST.properties in some areas overriding the value of </span><span style="white-space: pre-wrap">maxOutputSize because of this issue. So while it might mean a test run retains large .jtr that is truncated today, it seems a reasonable trade off when comparing to the frustrating of finding which test has failed.</span><br>
<span style="white-space: pre-wrap">
-Alan
</span>
</body>
</html>