Hoss Man created SOLR-13746:
-------------------------------
Summary: Apache jenkins needs JVM 11 upgraded to at least 11.0.3
(SSL bugs)
Key: SOLR-13746
URL: https://issues.apache.org/jira/browse/SOLR-13746
Project: Solr
Issue Type: Task
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Hoss Man
I just realized that back in June, there was a misscommunication between myself
& Uwe (and a lack of double checking on my part!) regarding upgrading the JVM
versions on our jenkins machines...
*
[http://mail-archives.apache.org/mod_mbox/lucene-dev/201906.mbox/%3calpine.DEB.2.11.1906181434350.23523@tray%3e]
*
[http://mail-archives.apache.org/mod_mbox/lucene-dev/201906.mbox/%3C00b301d52918$d27b2f60$77718e20$@thetaphi.de%3E]
...Uwe only updated the JVMs on _his_ policeman jenkins machines - the JVM used
on the _*apache*_ jenkins nodes is still (as of 2019-09-06) "11.0.1+13-LTS"
...
[https://builds.apache.org/view/L/view/Lucene/job/Lucene-Solr-Tests-master/3689/consoleText]
{noformat}
...
[java-info] java version "11.0.1"
[java-info] Java(TM) SE Runtime Environment (11.0.1+13-LTS, Oracle Corporation)
[java-info] Java HotSpot(TM) 64-Bit Server VM (11.0.1+13-LTS, Oracle
Corporation)
...
{noformat}
This means that even after the changes made in SOLR-12988 to re-enable SSL
testing on java11, all Apache jenkins 'master' builds, (including, AFAICT the
yetus / 'Patch Review' builds) are still SKIPping thousands of tests that use
SSL (either explicitly, or due to randomization) becauseof the logic in
SSLTestConfig to detects bad JVM versions an prevent confusion/spurious
failures.
We really need to get the jenkins nodes updated to openjdk 11.0.3 or 11.0.4
ASAP.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
