You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Robert Muir (Jira)" <ji...@apache.org> on 2021/10/24 11:57:00 UTC
[jira] [Commented] (LUCENE-9660) gradle task cache should not cache
--tests
[ https://issues.apache.org/jira/browse/LUCENE-9660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433428#comment-17433428 ]
Robert Muir commented on LUCENE-9660:
-------------------------------------
So we should be using {{cleanTest}} always?
There's never a time when i ask gradle to run tests, and don't want it to actually in fact, run the test.
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org