You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2020/08/31 17:13:00 UTC
[jira] [Updated] (LUCENE-9120) Ability to run gradle tests with
security auditing or any other JVM-level messaging
[ https://issues.apache.org/jira/browse/LUCENE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss updated LUCENE-9120:
--------------------------------
Parent: (was: LUCENE-9077)
Issue Type: Wish (was: Sub-task)
> 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: Wish
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org