[jira] [Commented] (LUCENE-9512) Add test-lock-factory to Gradle build

["Dawid Weiss (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-9512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192152#comment-17192152 ] 

Dawid Weiss commented on LUCENE-9512:
-------------------------------------

And why this can't be a regular test forking subprocesses, Uwe? You could pass the required stuff from gradle, but the test itself could just run as a regular JUnit test (in-process)?

> Add test-lock-factory to Gradle build
> -------------------------------------
>
>                 Key: LUCENE-9512
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9512
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: core/store
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>            Priority: Major
>
> When porting to Gradle, the following task was missed to be ported to Gradle:
> https://github.com/apache/lucene-solr/blob/branch_8x/lucene/core/build.xml#L148-L234
> This is somehow an integration test. It's not part of the test suite, as the code is part of main distribution and is a client-server implementation that has one coordinator to handle other JVMs to hammer a directories' lock factory.
> It may be included into the test suite, but as it spawns multiple JVMs (thats essential for it to work), I see this as a separate thing.
> I would like to implement that snippet of ANT code in Gradle and attach it to {{:lucene:core}}'s {{test}} task. If we have an integration test framework at some point we can make a real {{integTest}} out of it, but for now a simple Groovy script is fine.



--
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