[
https://issues.apache.org/jira/browse/LUCENE-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704436#comment-16704436
]
ASF subversion and git services commented on LUCENE-8579:
---------------------------------------------------------
Commit c074b97e79ffbbc914d1666e85cf725a1a7a8347 in lucene-solr's branch
refs/heads/master from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c074b97 ]
LUCENE-8579: Don't run bad apples when building a release.
> Don't run badapples when building a release
> -------------------------------------------
>
> Key: LUCENE-8579
> URL: https://issues.apache.org/jira/browse/LUCENE-8579
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Major
>
> Nick pinged me because his attempt to build a release failed because of Solr
> test failures. When looking at those, I noticed that a number of them were
> known flaky test that are already tagged as bad apples, eg.
> org.apache.solr.cloud.TestStressInPlaceUpdates.stressTest.
> We should disable badapples in the script to build a release, ie. something
> like
> {code:python}
> diff --git a/dev-tools/scripts/buildAndPushRelease.py
> b/dev-tools/scripts/buildAndPushRelease.py
> index 5a8f5cc..b557da2 100644
> --- a/dev-tools/scripts/buildAndPushRelease.py
> +++ b/dev-tools/scripts/buildAndPushRelease.py
> @@ -105,7 +105,7 @@ def prepare(root, version, gpgKeyID, gpgPassword):
> print(' Check DOAP files')
> checkDOAPfiles(version)
>
> - print(' ant clean test validate documentation-lint')
> + print(' ant -Dtests.badapples=false clean test validate
> documentation-lint')
> - run('ant clean test validate documentation-lint')
> + run('ant -Dtests.badapples=false clean test validate documentation-lint')
>
> open('rev.txt', mode='wb').write(rev.encode('UTF-8'))
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
