[
https://issues.apache.org/jira/browse/LUCENE-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013441#comment-14013441
]
Robert Muir commented on LUCENE-5645:
-------------------------------------
{quote}
It's been "supported" since the very beginning. A non-existent tests.seed or an
empty string are equivalent to the testing framework (and default to a randomly
picked seed).
{quote}
But thats not a general system property thing, its just something special that
the test-framework is doing, and only for this specific case of tests.seed?
Sorry, I have to try to stop the empty string :) Once it becomes "supported"
nobody will ever remove support for it. Time to make my stand.
> StringHelper should check for empty string of "tests.seed" system property
> --------------------------------------------------------------------------
>
> Key: LUCENE-5645
> URL: https://issues.apache.org/jira/browse/LUCENE-5645
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 4.8, 5.0
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: 4.8.1, 5.0
>
> Attachments: LUCENE-5645_StringHelper_empty_tests_seed_condition.patch
>
>
> As of LUCENE-5604 (committed to v4.8), StringHelper will initialize
> GOOD_FAST_HASH_SEED based on the system property "tests.seed" if it is set.
> Unfortunately it doesn't do an empty-string check, and it's common at least
> in my setup that copies Lucene's maven pom.xml that the string will be empty
> unless I set it on the command line. FWIW Randomized Testing does do an
> empty-string check.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
