-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[CI] EvilLoggerTests.testDeprecatedSettings failure #35990
Comments
Capturing the logging output for future investigation:
|
Pinging @elastic/es-core-infra |
Another one, does not reproduce locally on my mac |
Muted on 6.x - 6cf5c84 Looks like this has failed about once a day on darwin on 6.x since 28 November |
unmuting test to determine whether this is still an issue on the current branch. If it is found that this test does not fail in CI anymore, then this commit will remain and test will stay tested. related to elastic#35990.
unmuting test to determine whether this is still an issue on the current branch. If it is found that this test does not fail in CI anymore, then this commit will remain and test will stay tested. related to #35990.
And another here: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+multijob-darwin-compatibility/54/console These are enough to conclude the test is still problematic. I'll follow up to mute it. |
Re-muted in |
This test does not appear to have failed on 7.x or master, only on the 6.x line. The failure only appears possible if the deprecation log was not flushed, yet the implementation is a FileAppender which defaults to immediate flush. No work has been done on it in more than a year. Since 6.8 is the last active branch containing the failure, I propose to relax the file check portion of the test in the 6.8 branch. This will allow at least part of the test to resume effectiveness, while allowing us to consider this issue a historic mystery. |
I guess we should either re-enable to investigate the failure again or do as suggested here #35990 (comment) |
This test has been muted for a very long time, yet the underlying cause is still unknown, but it only occurs in 6.8. This commit removes the failing portion of the test so that we have some coverage. closes elastic#35990
This test has been muted for a very long time, yet the underlying cause is still unknown, but it only occurs in 6.8. This commit removes the failing portion of the test so that we have some coverage. closes #35990
Closed by #67465 |
This failed in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-darwin-compatibility/84/console but doesn't reproduce locally.
This looks suspiciously like #25680. It hasn't failed in the recent past, I'll be monitoring
The text was updated successfully, but these errors were encountered: