[
https://issues.apache.org/jira/browse/LUCENE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068625#comment-17068625
]
Erick Erickson edited comment on LUCENE-9120 at 3/27/20, 7:08 PM:
------------------------------------------------------------------
See:
[https://github.com/gradle/gradle/issues/11609|https://github.com/gradle/gradle/issues/11609.]
I've pinged the Gradle folks about this, we'll see what kind of response we
get.
was (Author: erickerickson):
See: [https://github.com/gradle/gradle/issues/11609.] I've pinged the Gradle
folks about this, we'll see what kind of response we get.
> Ability to run gradle tests with security auditing or any other JVM-level
> messaging
> -----------------------------------------------------------------------------------
>
> Key: LUCENE-9120
> URL: https://issues.apache.org/jira/browse/LUCENE-9120
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Minor
>
> Leaving as a separate task. I don't see any way of doing this with Gradle
> test runner as it uses sockets to pass stream outputs (this itself causes
> security auditing logs, leading to stack overflow).
> We'd need to run such corner cases with a different test runner (different
> task) or even run JUnit core runner directly as a forked Java process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
