-
Notifications
You must be signed in to change notification settings - Fork 32
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
FIM Windows Agent - Case: Windows audit interval changed #1973
Comments
Test Results 2021/10/04Tests were run with modules disabled, from new VMS created from scratch, each instance. After this results, help was requested from the core-fim team, who said the test passed for them.
Test Results 2021/10/05More debugging runs on new VMs. Only 1 test execution example added. Ran more than 20 instances during debbuging.
Test Results 2021/10/06On further research, it was found that the tests fail on Windows 10 systems. When testing on Windows Server 2016 and Windows7, tests pass successfully.
|
I attach results after to merged #1996 and #1984 with the fix to verify that it continues working.
|
Description
FIM tests have many flaws inconsistently. So our goal is to achieve consistent behavior.
The results are attached.
Pipeline parameters
Packages details
Packages Info
Note: The tag is
v4.2.1
but for now, to create it on jenkins you need to usev4.2.1-rc1
.local_internal_options.conf
Manager
Agent
Environment
pytest_args
-v --tier 0 --tier 1 --tier 2 --fim_mode="realtime" --fim_mode="whodata"
Development
Fix
test_fim/test_files/test_windows_audit_interval
to Windows.If the test work successfully after 2 times, you should see if other member could be verify that it woks successfully.
Tasks
scheduled
,realtime
, andwhodata
. Research if this case require all args, or only one.The text was updated successfully, but these errors were encountered: