Vivek Pandey wrote:
> Or you can always run with -Dmaven.test.skip=true.
That will make us ignore *all* test failures. Something
we must not do before commit!
>
> -vivek.
>
> Kedar Mhaswade wrote:
>> I get the failure with:
>> amxtest.AMXCoreTests:testAMXComplianceMonitorFailureCount
>>
>> It's not clear if that's the same as the one reported in 9355.
>>
>> BTW, can we temporarily disable the test so that we get a clean
>> run every time? When the bug is fixed, we can re-enable it.
>>
>> Thanks.
>>
>> Jane Young wrote:
>>> I know #2 is a known issue. See IT 9355
>>> and
>>> http://gf-hudson.sfbay.sun.com/hudson/job/gf-trunk-build-continuous/2205/artifact/bundles/QL-GP-report.html
>>>
>>>
>>> I'm not sure about #1.
>>> Are you getting total of 2 failures or 1?
>>
>>>
>>>
>>>
>>>
>>> Richard S. Hall wrote:
>>>> Hello,
>>>>
>>>> I am trying to make sure that Felix 2.0 is ready for release. My
>>>> latest run comes up with the following QL failures:
>>>>
>>>> 1. iterateAllSanityCheck
>>>> java.lang.NullPointerException
>>>> at
>>>> amxtest.AMXCoreTests.iterateAllSanityCheck(AMXCoreTests.java:94)
>>>> 2. testAMXComplianceMonitorFailureCount
>>>> java.lang.AssertionError: Server indicates that there are
>>>> non-compliant AMX MBean validator failures, failure count = 20,
>>>> examine the server log for failures
>>>> at
>>>> amxtest.AMXCoreTests.testAMXComplianceMonitorFailureCount(AMXCoreTests.java:112)
>>>>
>>>>
>>>> Are these normal failures in GF trunk?
>>>>
>>>> -> richard
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>