Folowing tests fails only on windows:

• org.jboss.as.test.integration.mgmt.access.LegacyConfigurationChangesHistoryTestCase
• org.jboss.as.test.integration.mgmt.access.ConfigurationChangesHistoryTestCase

Tests executes commands against cli for changing configuration. Then it executes cli command to see history of configuration changes and compares history with executed commands. Some times history lacks changes.

It seems that after executing command, in some cases server doesn't save config change to history, because it does not have enough time before execution of next command.

It was proven by running cli commands with timouts: https://github.com/nikitagibor/wildfly-core/commit/3f2f2dd4dddf7b5044c57ae459256bef970ab5d2 with no failures.

Since tests wait for execution of cli command to complete, it is more likely to be a server issue than testsuite issue.

Tests fail after this commit: https://github.com/wildfly/wildfly-core/commit/748402e746c31ba82e031c970971154c9501be2c

We run tests one commit before this one 100 times and it never fails once.
The bad commit fails one in 60 runs, with newer commits this frequency increase.

One of recent fails https://ci.wildfly.org/viewLog.html?buildId=261152&buildTypeId=WildFlyCore_MasterWindowsJdk11ea&tab=buildResultsDiv

Tests links:

• https://github.com/wildfly/wildfly-core/blob/main/testsuite/rbac/src/test/java/org/jboss/as/test/integration/mgmt/access/ConfigurationChangesHistoryTestCase.java
• https://github.com/wildfly/wildfly-core/blob/main/testsuite/rbac/src/test/java/org/jboss/as/test/integration/mgmt/access/LegacyConfigurationChangesHistoryTestCase.java