[
https://issues.apache.org/jira/browse/LUCENE-9660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261049#comment-17261049
]
Dawid Weiss commented on LUCENE-9660:
-------------------------------------
I may look into this to provide a local developer option to make tests always
run. I don't want it to be the default though (or even documented).
It's much like with 'check vs precommit' - there are some gradle conventions
you get used to after a while. Coming from maven or ant, it's a different
world, but it's not necessarily a bug...
> 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
