[
https://issues.apache.org/jira/browse/LUCENE-9660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433436#comment-17433436
]
Dawid Weiss commented on LUCENE-9660:
-------------------------------------
No, no. Normally tests will execute every time - the random seed is changing
from run to run, classes change, etc. If you rerun the same Gradle test task
(say, fix the seed and don't touch anything else) it will be up to date and
will be skipped. This scenario is so uncommon that I don't think it requires
special treatment. If you do encounter it, cleanTest first to force the test
task to run again
> 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
> Assignee: Dawid Weiss
> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
