See below. I have been seeing this a bit recently, At least the JMXAuditLogTestCase failure is due to that JBoss Modules has a WeakReference to the ServiceLoaders. When the weak reference is cleared this results (via the WeakReference's ReferenceQueue and the ModuleLoader's Reaper) in a call to unregister the MBean associated with the ServiceLoader, which shows up as an additional unexpected entry in the AuditLog. This clearing of the weak reference is unpredictable and can happen at any time. I plan to fix this test test today, and to add a better message to the AuditLogBootingSyslogTest. Example failures: https://ci.wildfly.org/viewLog.html?buildId=65226&buildTypeId=WildFly... https://ci.wildfly.org/viewLog.html?buildId=65225&buildTypeId=WildFly...