[
https://issues.apache.org/jira/browse/LUCENE-9660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261048#comment-17261048
]
Dawid Weiss commented on LUCENE-9660:
-------------------------------------
This is by design and it should not be changed. If you change *any* parameter
or dependency of the incremental build, the test task will run again. It's
typically enough to not specify the random seed - if the seed is random, it
re-runs the test pretty much automatically every time.
See here for more information:
https://github.com/apache/lucene-solr/blob/master/help/tests.txt#L92-L103
Disabling this functionality is not in your favour in the long run. For
multi-module projects 'gradlew check' runs only those tasks that really changed
somehow - including tests for just those modules that have changed.
> gradle task cache should not cache --tests
> ------------------------------------------
>
> Key: LUCENE-9660
> URL: https://issues.apache.org/jira/browse/LUCENE-9660
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: David Smiley
> Priority: Minor
>
> I recently ran a specific test at the CLI via gradle to see if a particular
> build failure repeats. It includes the {{--tests}} command line option to
> specify the test. The test passed. Later I wanted to run it again; I
> suspected it might be flakey. Gradle completed in 10 seconds, and I'm
> certain it didn't actually run the test. There was no printout and the
> build/test-results/test/outputs/... from the test run still had not changed
> from previously.
> Mike Drob informed me of "gradlew cleanTest" but I'd prefer to not have to
> know about that, at least not for the specific case of wanting to execute a
> specific test.
> CC [~dweiss]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]