[ https://issues.apache.org/jira/browse/LUCENE-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943222#comment-16943222 ]
ASF subversion and git services commented on LUCENE-8991: --------------------------------------------------------- Commit 10da07a396777e3e7cfb091c5dec826b6df11284 in lucene-solr's branch refs/heads/master from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=10da07a ] LUCENE-8991: disable java.util.HashMap assertions to avoid spurious vailures due to JDK-8205399 > disable java.util.HashMap assertions to avoid spurious vailures due to > JDK-8205399 > ---------------------------------------------------------------------------------- > > Key: LUCENE-8991 > URL: https://issues.apache.org/jira/browse/LUCENE-8991 > Project: Lucene - Core > Issue Type: Bug > Reporter: Chris M. Hostetter > Priority: Major > Labels: Java10, Java11 > Attachments: LUCENE-8991.patch, LUCENE-8991.patch > > > An incredibly common class of jenkins failure (at least in Solr tests) stems > from triggering assertion failures in java.util.HashMap -- evidently > triggering bug JDK-8205399, first introduced in java-10, and fixed in > java-12, but has never been backported to any java-10 or java-11 bug fix > release... > https://bugs.openjdk.java.net/browse/JDK-8205399 > SOLR-13653 tracks how this bug can affect Solr users, but I think it would > make sense to disable java.util.HashMap in our build system to reduce the > confusing failures when users/jenkins runs tests, since there is nothing we > can do to work around this when testing with java-11 (or java-10 on branch_8x) -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org