-
Notifications
You must be signed in to change notification settings - Fork 30
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
Failed Windows Logcollector tests on 4.8.0 Beta 2 #5034
Comments
Might this be related to wazuh/wazuh#21791? If it is, this is a stopper. Otherwise, let's add it to the backlog. |
AnalysisNot reproducedAfter a thorough investigation of this error, I have not been able to reproduce it at any time locally. I have run the entire logcollector test suite multiple times, and on a few occasions I have encountered random and flaky errors in other tests, but no in the I rule out that it could be related to the change of issue wazuh/wazuh#21791, as the test seems to be working without any problems. The random flaky problems encountered seem to be related to disconnections with the manager during testing. |
I joined this research. There was concern that the agent, which was monitoring the files, might be blocking some of them. To investigate, we configured the agent to monitor a file with Logcollector and then attempted to delete it while it was open. There were no issues encountered, leading us to conclude that the agent does not have this bug and that the test may have some other problem. ProposalOur proposal is to enhance the test to report which file still exists after the deletion attempt. This could provide a clue to finding the root cause of the issue. ConclusionAt the moment, this issue is not a release stopper. |
Description
During release testing 4.8.0 Beta 2 IT suite execution, a Logcollector test failed on Windows endpoint due to a folder not being empty and could not be removed. Mey be caused by race condition.
This tests have not been migrated to github actions.
The displayed error in all tests occurred during test teardown:
More research is needed.
The text was updated successfully, but these errors were encountered: