Mute SSLTrustRestrictionsTests on JDK 11

This commit adds an assumption to two test methods in
SSLTrustRestrictionsTests that we are not on JDK 11 as the tests
currently fail there.

Relates #29989
This commit is contained in:
Daniel Mitterdorfer 2018-07-31 16:17:28 +02:00
parent b42765c82f
commit 5f302580f9
1 changed files with 5 additions and 0 deletions

View File

@ -7,6 +7,7 @@ package org.elasticsearch.xpack.ssl;
import org.apache.logging.log4j.message.ParameterizedMessage;
import org.elasticsearch.ElasticsearchException;
import org.elasticsearch.bootstrap.JavaVersion;
import org.elasticsearch.common.io.PathUtils;
import org.elasticsearch.common.settings.Settings;
import org.elasticsearch.common.transport.TransportAddress;
@ -173,6 +174,8 @@ public class SSLTrustRestrictionsTests extends SecurityIntegTestCase {
}
public void testCertificateWithUntrustedNameFails() throws Exception {
// see https://github.com/elastic/elasticsearch/issues/29989
assumeTrue("test fails on JDK 11 currently", JavaVersion.current().compareTo(JavaVersion.parse("11")) < 0);
writeRestrictions("*.trusted");
try {
tryConnect(untrustedCert);
@ -183,6 +186,8 @@ public class SSLTrustRestrictionsTests extends SecurityIntegTestCase {
}
public void testRestrictionsAreReloaded() throws Exception {
// see https://github.com/elastic/elasticsearch/issues/29989
assumeTrue("test fails on JDK 11 currently", JavaVersion.current().compareTo(JavaVersion.parse("11")) < 0);
writeRestrictions("*");
assertBusy(() -> {
try {