[LUCENE-9660] gradle task cache should not cache --tests

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 9.0
• Component/s: general/build
• Lucene Fields: New
• Assignee: Dawid Weiss
• Reporter: David Smiley
• Created: 07/Jan/21 22:16
• Updated: 28/Aug/22 16:12
• Resolved: 25/Oct/21 12:51

Description

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

Issue Links

• links to: GitHub Pull Request #410