-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Auditbeat] Flaky file_integrity.test_recursive test #7731
Comments
It looks like the OS never sent an event for |
There have been spurious test failures in test_file_integrity.Test.test_recursive (elastic#7731). This makes sure all errors encountered in recursiveWatcher are caught and logged, and also adds a debug message when a new recursive watch is added.
Even before Maybe something related to the concurrent map access in #8009 in which case #8027 should help. I opened #8087 to add error catching everywhere the event could have been held up before being reported. If this happens again, we should have more information either way - a new error message or we've excluded a possible cause and need to dive into |
I've merged #8087. I suggest we keep this issue open for a month or so to see if it still happens. |
There have been spurious test failures in test_file_integrity.Test.test_recursive (#7731). This makes sure all errors encountered in recursiveWatcher are caught and logged, and also adds a debug message when a new recursive watch is added.
There have been spurious test failures in test_file_integrity.Test.test_recursive (elastic#7731). This makes sure all errors encountered in recursiveWatcher are caught and logged, and also adds a debug message when a new recursive watch is added. (cherry picked from commit e5f16e2)
Skipping this test as it was flaky several times. See elastic#7731 for report.
Skipping this test as it was flaky several times. See #7731 for report.
This exact test failure does not seem to be happening anymore. There were others in this test that were fixed since then. Closing for now. |
Error:
Log
The text was updated successfully, but these errors were encountered: