-
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
Improve error catching for recursiveWatcher #8087
Conversation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for investigating this failures @cwurm
@cwurm I hit the error agai here: https://beats-ci.elastic.co/job/elastic+beats+pull-request+multijob-linux/6383/beat=auditbeat,label=ubuntu/testReport/junit/test_file_integrity/Test/test_recursive/ It's against 6.x. I would suggest to backport this fix also to 6.x? |
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)
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.