-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] MonitoringTribeTests failed due to setting SetOnce twice #42216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
:Data Management/Monitoring
:Security/TLS
SSL/TLS, Certificates
Team:Data Management
Meta label for data/management team
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-core-features |
Pinging @elastic/es-security |
Relates: #42004 |
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
May 24, 2019
This test is failing on RHEL8, additional logging will help track down the cause. Relates: elastic#42216, elastic#42210
tvernum
added a commit
that referenced
this issue
May 24, 2019
This issue is on hold because our RHEL8 builds were breaking unexpectedly, so they're not currently included in the unix matrix builds. |
Tribes is no longer a thing, so I am going to close this since it's almost two years old. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/Monitoring
:Security/TLS
SSL/TLS, Certificates
Team:Data Management
Meta label for data/management team
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
MonitoringTribeTests
failed in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+multijob-unix-compatibility/os=redhat-8/200/consoleThe underlying error was:
This did not reproduce locally using:
Since it's a double setting of a
SetOnce
I also tried to reproduce by running the whole suite:That didn't reproduce either.
The text was updated successfully, but these errors were encountered: