elastic / elasticsearch

Free and Open Source, Distributed, RESTful Search Engine
https://www.elastic.co/products/elasticsearch
Other
1.33k stars 24.87k forks source link

[CI] testDriverConfigurationWithSSLInURL fails #41557

Open dnhatn opened 5 years ago

dnhatn commented 5 years ago

testDriverConfigurationWithSSLInURL starts failing on CI after https://github.com/elastic/elasticsearch/commit/0ca375ed42f420f4c7c4a8c489a2ecc328db3648.

  2> java.lang.AssertionError: Driver registration should have been successful. Error: java.sql.SQLException: No suitable driver
        at __randomizedtesting.SeedInfo.seed([D912BBBA5B9BCB6B:A9E1C8ACED9F587D]:0)
        at org.junit.Assert.fail(Assert.java:88)
        at org.elasticsearch.xpack.sql.jdbc.JdbcConfigurationTests.testDriverConfigurationWithSSLInURL(JdbcConfigurationTests.java:265)

I can't reproduce this locally.

./gradlew :x-pack:plugin:sql:jdbc:test --tests "org.elasticsearch.xpack.sql.jdbc.JdbcConfigurationTests.testDriverConfigurationWithSSLInURL" \
  -Dtests.seed=D912BBBA5B9BCB6B \
  -Dtests.security.manager=true \
  -Dtests.locale=mg-MG \
  -Dtests.timezone=America/Dawson_Creek \
  -Dcompiler.java=12 \
  -Druntime.java=11

Relates #41283

elasticmachine commented 5 years ago

Pinging @elastic/es-distributed

dnhatn commented 5 years ago

@tbrooks8 Can you please have a look? Thank you!

Tim-Brooks commented 5 years ago

I don't think this relates to my change.

This fails on 7.0 (my change is not on 7.0):

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.0+artifactory/277/console

And on master prior to my commit:

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+artifactory/548/console

dnhatn commented 5 years ago

@tbrooks8 Good catch. I missed that one.

elasticmachine commented 5 years ago

Pinging @elastic/es-search

astefan commented 5 years ago

Had a first look at this one, but I can't see how this could fail unless something did go wrong on the CI infra. And can't reproduce locally either. @dnhatn should I allow this test to run again and maybe a future failure to reveal more on the environment around the failure?

dnhatn commented 5 years ago

@astefan Thanks for looking. Please unmute the test and add whatever log that you need.

astefan commented 5 years ago

Tests are re-enabled now.

alpar-t commented 5 years ago

These seem to reproduce constantly e.x. https://gradle-enterprise.elastic.co/s/rtnrsij5womtq/tests/fswe7cwgla35g-a6pci3z7j2mns

I'm going to mute them again to prevent them from masking other windows failures.

romseygeek commented 5 years ago

This is also failing on 7.x (eg https://gradle-enterprise.elastic.co/s/savqudvq7jria/console-log?task=:x-pack:plugin:sql:jdbc:test), so I will mute it there.

iverase commented 5 years ago

I am muting branches 7.5 and 7.4 as they are failing there as well.

astefan commented 5 years ago

@atorok @iverase @romseygeek were you able to repro any of these locally?

dimitris-athanasiou commented 5 years ago

@atorok Your mute commit https://github.com/elastic/elasticsearch/commit/3d4a7d0c6cfb3516bd1e94213788b66b42ca9cf7 seems to not actually add any @AwaitsFix. Am I missing something? Just got another failure in 7.4 and looked at all the mutes which are backports of your commit.

alpar-t commented 5 years ago

@dimitris-athanasiou It adds assumeFalse to conditionally mute the test on windows only

dimitris-athanasiou commented 5 years ago

Ah, I see. It seems we're also catching failures in darwin (e.g. https://gradle-enterprise.elastic.co/s/wnuyywau7seka/tests/fswe7cwgla35g-a6pci3z7j2mns). I'll mute using @AwaitsFix.

astefan commented 5 years ago

@dimitris-athanasiou were you able to repro this locally?

dimitris-athanasiou commented 5 years ago

@astefan No, it doesn't reproduce locally unfortunately.

elasticsearchmachine commented 1 year ago

Pinging @elastic/es-ql (Team:QL)

elasticsearchmachine commented 10 months ago

Pinging @elastic/es-analytical-engine (Team:Analytics)

elasticsearchmachine commented 2 weeks ago

This issue has been closed because it has been open for too long with no activity.

Any muted tests that were associated with this issue have been unmuted.

If the tests begin failing again, a new issue will be opened, and they may be muted again.

elasticsearchmachine commented 1 week ago

This issue is getting re-opened because there are still AwaitsFix mutes for the given test. It will likely be closed again in the future.