[ 
https://issues.apache.org/jira/browse/SOLR-12988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-12988:
----------------------------
    Attachment: SOLR-12988.patch
        Status: Open  (was: Open)

I'm attaching a patch I've worked up which:
 * Reinstates SSL testing, both explicit and randomized
 * modifies SSLTestConfig constructor to {{assumeSslIsSafeToTest()}}
 * implements {{assumeSslIsSafeToTest()}} using a (safe to backport) regex 
based helper method that is called on the JVM_VERSION
 ** the regex is based on my research as to the SSL bugs we've definitely seen 
in past jenkins builds, and which JDK builds they exist in
 * includes unit of the regex helper method to try and ensure no false 
negatives/positives

...I think this is good to go once we get the JDKs upgraded on our jenkins 
machines, but I'm still testing & I'd appreciate sanity checking eyeballs from 
other folks.

(in particular does anyone know how to find a list of all "official" ea builds 
from OpenJDK? I _believe_ "13-ea+26" was the first "13-ea" release, which 
should means only the pre-ea "testing" versions of 13 are affected by 
JDK-8224829, but I don't actually know how to verify that)

> Skip running tests with SSL on Java 11 to 11.0.2
> ------------------------------------------------
>
>                 Key: SOLR-12988
>                 URL: https://issues.apache.org/jira/browse/SOLR-12988
>             Project: Solr
>          Issue Type: Test
>            Reporter: Hoss Man
>            Assignee: Cao Manh Dat
>            Priority: Major
>              Labels: Java11, Java12
>         Attachments: SOLR-12988.patch, SOLR-12988.patch, SOLR-13413.patch
>
>
> HTTPCLIENT-1967 indicates that HttpClient can't be used properly with 
> TLSv1.3. It caused some test failures below, therefore we should skip running 
> tests with SSL on Java 11 to 11.0.2.
> TestMiniSolrCloudClusterSSL.testSslWithCheckPeerName seems to fail 100% of 
> the time when run with java11 (or java12), regardless of seed, on both master 
> & 7x.
> The nature of the problem and the way our htp stack works suggests it *may* 
> ultimately be a jetty bug (perhaps related to [jetty 
> issue#2711|https://github.com/eclipse/jetty.project/issues/2711]?)
> *HOWEVER* ... as far as i can tell, whatever the root cause is, seems to have 
> been fixed on the {{jira/http2}} branch (as of 
> 52bc163dc1804c31af09c1fba99647005da415ad) which should hopefully be getting 
> merged to master soon.
> Filing this issue largely for tracking purpose, although we may also want to 
> use it for discussions/considerations of other backports/fixes to 7x



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to