You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2021/10/26 06:46:00 UTC
[jira] [Comment Edited] (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=17434140#comment-17434140 ]
Dawid Weiss edited comment on LUCENE-9660 at 10/26/21, 6:45 AM:
----------------------------------------------------------------
As a side note - the 'cleanX' convention doesn't rerun all tasks, it just wipes the outputs of task X. So a 'cleanX' wouldn't result in java recompiling classes or anything - it'd just rerun the test task (much like forced up-to-date):
{code}
> gradlew -p lucene\analysis\kuromoji cleanTest test -Ptests.neverUpToDate=false -Ptests.seed=deadbeef --console=plain
...
> Task :lucene:analysis:kuromoji:cleanTest
> Task :lucene:analysis:kuromoji:processResources UP-TO-DATE
> Task :lucene:analysis:kuromoji:copyTestResources UP-TO-DATE
...
> Task :lucene:analysis:kuromoji:compileTestJava UP-TO-DATE
> Task :lucene:analysis:kuromoji:testClasses UP-TO-DATE
> Task :lucene:analysis:kuromoji:test
...
{code}
was (Author: dweiss):
As a side note - the 'cleanX' convention doesn't rerun all tasks, it just wipes the outputs of the task X. So a 'cleanX' wouldn't result in java recompiling classes or anything - it'd just rerun the test task (much like forced up-to-date):
{code}
> gradlew -p lucene\analysis\kuromoji cleanTest test -Ptests.neverUpToDate=false -Ptests.seed=deadbeef --console=plain
...
> Task :lucene:analysis:kuromoji:cleanTest
> Task :lucene:analysis:kuromoji:processResources UP-TO-DATE
> Task :lucene:analysis:kuromoji:copyTestResources UP-TO-DATE
...
> Task :lucene:analysis:kuromoji:compileTestJava UP-TO-DATE
> Task :lucene:analysis:kuromoji:testClasses UP-TO-DATE
> Task :lucene:analysis:kuromoji:test
...
{code}
> 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
> Fix For: main (9.0)
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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