[jboss-dev] [Fwd: JBoss-AS-5.0.x-TestSuite-sun15 - Build # 1097 - Unstable!]

Dimitris Andreadis dandread at redhat.com
Tue Nov 25 07:21:24 EST 2008


Let's wait for a full run to verify the culprit and we'll reply the updates after that.

Kabir Khan wrote:
> Yes, I found that r81443 which is the upgrade to reflect 2.0.1.GA gives 
> the org.jboss.test.aop.test failures mentioned.
> The aop tests run fine in current as trunk with both aop 2.0.0.GA and 
> 2.0.0.SP1.
> 
> Dimitris, can I reapply AOP 2.0.0.SP1?
> 
> On 25 Nov 2008, at 12:04, Ales Justin wrote:
> 
>> It must be my change to reflect 2.0.1.GA,
>> as I see some failures in MC/Kernel. :-(
>>
>> I'm looking into it now.
>>
>> Kabir Khan wrote:
>>> Am updating now. In the meantime, r81442 passed for me and r81446 failed
>>> On 25 Nov 2008, at 11:19, Dimitris Andreadis wrote:
>>>> Can you try with the latest trunk? I just did some rollbacks.
>>>>
>>>> Kabir Khan wrote:
>>>>> On 25 Nov 2008, at 06:45, Anil Saldhana wrote:
>>>>>> Scott Stark wrote:
>>>>>>> but as soon as the second set of tests started running they are 
>>>>>>> failing. I'm rerunning with aop 2.0.0.GA
>>>>>>>
>>>>>>> Scott Stark wrote:
>>>>>>>> I would look at the upgrade to aop 2.0.0.SP1 from 2.0.0.GA. So 
>>>>>>>> far the tests are running for me (ant tests-clustering-all-stacks).
>>>>>>>>
>>>>>> Kabir did mention that some AS aop tests failed with the upgrade, 
>>>>>> on hudson, even though they passed locally.
>>>>>>
>>>>>> It is interesting because 2.0.0.SP1 had just privileged blocks 
>>>>>> introduced with no change in functionality.
>>>>> I am trying to figure out what happened. Locally AS trunk fails for 
>>>>> the following aop tests
>>>>> org.jboss.test.aop.test.ScopedExtenderBaseLoadedScopedNoParentDelegationTestCase 
>>>>> org.jboss.test.aop.test.ScopedUnitTestCase
>>>>> with both AOP 2.0.0.GA and AOP 2.0.0.SP1. Going back it passes with 
>>>>> both for AS trunk r81441 and fails for AS trunk r814551. Looking at 
>>>>> the commits between there, I cannot see anything obvious, but I'll 
>>>>> keep investigating
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development



More information about the jboss-development mailing list