[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953893#comment-15953893
]
Hoss Man commented on SOLR-10338:
---------------------------------
Jekinks JDK9 builds are freaking out over this change...
{noformat}
765 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.analysis.TestFoldingMultitermExtrasQuery
Error Message:
expected:<[SHA1PRN]G> but was:<[DRB]G>
Stack Trace:
org.junit.ComparisonFailure: expected:<[SHA1PRN]G> but was:<[DRB]G>
at __randomizedtesting.SeedInfo.seed([C3B5A016F8A4D7E1]:0)
at org.junit.Assert.assertEquals(Assert.java:125)
at org.junit.Assert.assertEquals(Assert.java:147)
at
org.apache.solr.SolrTestCaseJ4.assertNonBlockingRandomGeneratorAvailable(SolrTestCaseJ4.java:2440)
{noformat}
[[email protected]] - i think we need to roll this back and re-consider?
(i suspect we just need to tweak the assert to accept some new options, but
rollback seem appropriate until we have time for more testing)
> 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
> Fix For: master (7.0), 6.6
>
> Attachments: 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
