[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939047#comment-15939047
]
Hoss Man commented on SOLR-10338:
---------------------------------
bq. As far as the IDEs concerned, we could also do that. Probably this is not
that much of a pain as the ant setting, because on your desktop you usually
have just enough entropy and you run only parts of the test suite at once.
bq. That \@BeforeClass approach is much stricter. This would mean that if the
flag is not set, all Solr tests fail, and the output of the test run will
become useless. Maybe a single test is just enough as an indicator test. Or are
you thinking of failing the tests fast and to prevent false negative tests?
In both cases i am specifically thinking about failing fast -- regardless of
how the tests are run -- to help ensure that we don't get false negatives from
tests because people don't have enough entroy *AND* are somehow running the
test in a way that avoids our efforts at "reproducibility" in what the source
of entropy is. (so that there should always be enough entroy)
> Configure SecureRandom non blocking
> -----------------------------------
>
> Key: SOLR-10338
> URL: https://issues.apache.org/jira/browse/SOLR-10338
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mihaly Toth
> Assignee: Mark Miller
> Fix For: 4.9, 6.0
>
> Attachments: 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
