-
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
[Filebeat] Flaky test_clean_inactive test #8102
Comments
With the nature of VMs and disk, writing or reading a file can be out of sync. Instead of only sleeping only the windows case we sleep on every tested platform before asserting the content of the registry. closes elastic#8102
With the nature of VMs and disk, writing or reading a file can be out of sync. Instead of only sleeping only the windows case we sleep on every tested platform before asserting the content of the registry. closes #8102
With the nature of VMs and disk, writing or reading a file can be out of sync. Instead of only sleeping only the windows case we sleep on every tested platform before asserting the content of the registry. closes elastic#8102 (cherry picked from commit ca78d74)
The test failed again on Windows: This seems like a new error, as we are getting permission denied.
Logs
|
`test_clean_inactive` (elastic#8102) and `test_clean_removed` (elastic#7690) have been flaky recently again on Windows. Skipping these test for Windows.
Here more recent artifacts from a build: |
This test failed on macOS on Travis |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Seen in https://beats-ci.elastic.co/job/elastic+beats+pull-request+multijob-darwin/3672/beat=filebeat,label=macosx/testReport/junit/test_registrar/Test/test_clean_inactive/ (darwin build)
The text was updated successfully, but these errors were encountered: