[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414597#comment-16414597
]
Hoss Man commented on SOLR-10338:
---------------------------------
bq. I think SolrTestCaseJ4's insistence on this is a bit of an over-reach for
external projects that want to use solr-test-framework. It's well intentioned
but creates an annoying hassle that randomly occurs.
I'm no longer convinced i even understand what "this" is in the context of our
current discussion, since the changes made SOLR-10338 do not involve
SolrTestCaseJ4 do not involve anything that should "randomly occur" ... any
assertion from the code committed in this issue should occur reliably 100% of
the time assuming they are re-run on the same JVM.
I think this dicussion should be moved to a new jira, with a new subject, and a
detailed description of exactly what error message you are seeing, and what
your test code looks like, and the specifics of your JVM.
> Configure SecureRandom non blocking for tests.
> ----------------------------------------------
>
> Key: SOLR-10338
> URL: https://issues.apache.org/jira/browse/SOLR-10338
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mihaly Toth
> Assignee: Mark Miller
> Priority: Major
> Fix For: 7.1, master (8.0)
>
> Attachments: SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch
>
>
> It would be best if SecureRandom could be made non blocking. In that case we
> could get rid of random entropy exhaustion issue related to all usages of
> SecureRandom.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
