Bug 785237

Summary: Get DriftManagerBeanTest working on jenkins
Product: [Other] RHQ Project Reporter: Jay Shaughnessy <jshaughn>
Component: TestsAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED WORKSFORME QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: medium    
Version: 4.3CC: hrupp, ian.springer
Target Milestone: ---   
Target Release: JON 3.1.1   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-08 20:10:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jay Shaughnessy 2012-01-27 18:19:07 UTC
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?

Comment 1 Mike Foley 2012-01-30 16:43:09 UTC
setting priority per 12/30/2012 BZ triage mfoley, ccrouch, loleary, asantos

Comment 2 Jay Shaughnessy 2012-01-30 19:22:50 UTC
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.

Comment 4 Jay Shaughnessy 2012-06-08 20:10:45 UTC
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.