This is actually an accidental (?) clash between Lucene's system property
and what's in defaults-tests.gradle.
You can manually prepend true || ... to the following in
defaults-tests.gradle.
def verboseMode = resolvedTestOption("tests.verbose").toBoolean()
I can't remember why it aligns with Lucene's logger. Maybe it should/could
be a
separate property? I find it difficult to come up with a reasonable name
though.
D.
On Tue, Dec 12, 2023 at 8:03 PM Michael McCandless <
luc...@mikemccandless.com> wrote:
> Hi Team,
>
> This is prolly a Dawid question...
>
> Sometimes I want to run a test (like a slow Monster test), seeing its
> ongoing musings popping out on the console in "real time" (not buffered).
>
> I can do this today by adding "-Dtests.verbose=true" to the ./gradlew
> invocation that's running the test.
>
> But that also turns on LuceneTestCase.VERBOSE which sometimes produces
> insane amounts of mostly not helpful content.
>
> Is there any way to do the first (stream console output) without the
> second (mega verbosity enabled)?
>
> Thanks,
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
