Can we get a BZ to track fixing this issues with the test infrastructure. ----- Original Message ----- That's correct, it is not. It was not executing before I did all that work on the server jar tests last week. During that work I did execute it standalone, fix it, and got the tests passing. But when executed in a complete RHQ test run it causes a yet-to-be-explained issue that has to do with, I think, some strange interaction with the itests module. I wanted to discuss it with jsanda, but he's on pto, so next week. Bottom line is that the tests pass, it's an issue with testing only. > > On 1/26/2012 8:06 PM, Charles Crouch wrote: >> http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=9cc28466baff7e226f948b4227cf70f4ef14b078 >> >> This commit seems to imply that its not?
setting priority per 12/30/2012 BZ triage mfoley, ccrouch, loleary, asantos
spent a few minutes talk about this with jsanda but no real progress. Also, failed to reproduce the problem locally, so really not sure what the issue is when run on jenkins.
Given the variety of changes we've made, perhaps due to new versions of testng, maven, surefire, etc, this unexplained problem now seems to be gone and the tests are passing.