[ https://issues.jboss.org/browse/JBTM-949?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-949: ------------------------------- Fix Version/s: 5.0.0.M2 (was: 5.0.0.Final) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-949?page=com.atlassian.jira.plugin.s... ] Paul Robinson commented on JBTM-949: ------------------------------------ We have now included the XTS recovery tests in CI. This job automated the process of running the tests and generating the trace logs for inspection. Since then we've had many failures from these tests. Two bugs in the code were found and a few bugs in the tests. All these failures where due to timing issues that do not seem to occur on a fast machine. Hence the reason why they where not spotted until now, as the recovery tests have always been ran on powerful machines. Whilst fixing these issues, I've had chance to understand, a lot better, how these tests work, and we've come to the conclusion that the automated part of the test actually tests everything that really matters. The Byteman script is used to crash the system when it reaches a particular state. If this state is not met, then the test fails. The system is then recovered and the tests check that the right outcome is sent to all participants and that the TX log is tidied up. Again, the test fails if this was not the case. The additional benefit of checking the trace logs is that we can ensure the correct path was taken throughout the test. However, this process is very time consuming and, in my experience, has never shown up any bugs, other than cosmetic issues with the Byteman scripts (usually missmatch between the log messages and the expected log message). These logs are very useful when tracking down the cause of a failure, so we should still keep them, but not verify them by eye during each release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-949?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-949: ------------------------------- Fix Version/s: 4.17.0 (was: 5.0.0.M2) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira