dev@glassfish.java.net

Re: QL failure.

From: Nandini Ektare <Nandini.Ektare_at_Sun.COM>
Date: Wed, 20 May 2009 16:13:02 -0700

Sevo-Zenzerovic wrote:
> Ming, this is passing for me...
>
> Now, sorry to offload this but I do have something rather urgent to
> take care of - could someone who experienced QL failure on their
> Windows system take glassfish.zip file produced by continuous build?
I ran QL successfully against the continuous build Snjezana had
referenced
(http://gf-hudson.sfbay.sun.com/hudson/job/gf-trunk-build-continuous/ )
That passes without any failures.

But the zip coming out of the trunk's build has this error. What is the
difference between the two (if any)?

Nandini
> This is still "developer" distribution, but the difference is that it
> is built on Unix as opposed to Windows which may make difference when
> it comes to things such as EOL characters and such...
>
> Ming Zhang wrote:
>
>> Hi Snjezana,
>>
>> Just for the debug purpose, can you/or someone try QL against the IPS
>> build on windows also?
>> http://gf-hudson.sfbay/hudson/job/trunk-nightly/lastSuccessfulBuild/artifact/bundles/glassfish-v3-b48-05_20_2009.zip
>>
>> So that we are on the same page.
>>
>> Thanks,
>> Ming
>>
>> Snjezana Sevo-Zenzerovic wrote:
>>
>>> Given that the development build now differs from IPS build only in
>>> the presence of IPS metadata, this is *very* slim possibility....
>>>
>>>
>>> Ming Zhang wrote:
>>>
>>>> But continuous QL job is running on solaris/linux, right? I suspect
>>>> the development build on windows has problem.
>>>> Thanks,
>>>> Ming
>>>>
>>>> Snjezana Sevo-Zenzerovic wrote:
>>>>
>>>>> No, it couldn't because continuous QL job itself is running on
>>>>> non-IPS distributions...
>>>>>
>>>>> Ming Zhang wrote:
>>>>>
>>>>>> Byron brought up the failures 2 days ago. I tried to reproduce
>>>>>> the QL failures with glassfish-v3-b48-05_18_2009.zip on my
>>>>>> Windows Vista and couldn't see the errors. Today I used
>>>>>> glassfish-v3-b48-05_20_2009.zip (trunk nightly) and still all QL
>>>>>> tests passed. Could this be due to IPS vs development build?
>>>>>>
>>>>>> Thanks,
>>>>>> Mings
>>>>>>
>>>>>> Byron Nevins wrote:
>>>>>>
>>>>>>> Yes, I'm not positive but it looks just right.
>>>>>>>
>>>>>>> It was "ejb-something", 1 failure, 2 skips
>>>>>>> over and over again
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Marina Vatkina wrote:
>>>>>>>
>>>>>>>> Byron,
>>>>>>>>
>>>>>>>> Are these the same failures that you saw?
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> -marina
>>>>>>>>
>>>>>>>> Nandini Ektare wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks Dies.
>>>>>>>>> Jane, even I use windows.
>>>>>>>>>
>>>>>>>>> -Nandini
>>>>>>>>>
>>>>>>>>> Dies Koper wrote:
>>>>>>>>>
>>>>>>>>>> Hi Nandini, Jane,
>>>>>>>>>>
>>>>>>>>>> I've been seeing the same failure during QL for two days.
>>>>>>>>>> That's on Windows.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Dies
>>>>>>>>>>
>>>>>>>>>> Jane Young wrote:
>>>>>>>>>>
>>>>>>>>>>> Not sure what's going on with your build.
>>>>>>>>>>> I just did a "mvn clean install" on v3 trunk workspace and
>>>>>>>>>>> have no problem running QL tests.
>>>>>>>>>>>
>>>>>>>>>>> I'm using a Mac.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Nandini Ektare wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Jane Young wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> QL tests are passing on Hudson' v3 trunk continuous build.
>>>>>>>>>>>>> http://hudson.glassfish.org/job/gf-trunk-build-continuous/
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you compile with "mvn clean install" to make sure
>>>>>>>>>>>>> your build is from a clean target workspace and try
>>>>>>>>>>>>> running QL again?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hmm...I removed maven repo and did a mvn -U clean install.
>>>>>>>>>>>> I still get this error.
>>>>>>>>>>>>
>>>>>>>>>>>> Is there any new additional System property that needs to
>>>>>>>>>>>> be configured. The error seems to suggest that.
>>>>>>>>>>>>
>>>>>>>>>>>>> Nandini Ektare wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> With a latest fresh checkout of v3 trunk I see the
>>>>>>>>>>>>>> following issue. Is this a known issue ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [testng] FAILED: helloRemote
>>>>>>>>>>>>>> [testng] javax.naming.NoInitialContextException: Need to
>>>>>>>>>>>>>> specify class name in environment or system property, or as
>>>>>>>>>>>>>> applet parameter, or in an application resource file:
>>>>>>>>>>>>>> java.naming.factory.initial
>>>>>>>>>>>>>> [testng] at
>>>>>>>>>>>>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [testng] at
>>>>>>>>>>>>>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [testng] at
>>>>>>>>>>>>>> javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [testng] at
>>>>>>>>>>>>>> javax.naming.InitialContext.lookup(InitialContext.java:392)
>>>>>>>>>>>>>> [testng] at
>>>>>>>>>>>>>> test.ejb.remoteview.RemoteViewTestNG.helloRemote(RemoteViewTestNG.java:18)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [testng] ... Removed 22 stack frames
>>>>>>>>>>>>>> [testng] SKIPPED: nonPortableGlobal
>>>>>>>>>>>>>> [testng] SKIPPED: portableGlobal
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [testng] ===============================================
>>>>>>>>>>>>>> [testng] ejb_remoteview
>>>>>>>>>>>>>> [testng] Tests run: 3, Failures: 1, Skips: 2
>>>>>>>>>>>>>> [testng] ===============================================
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Nandini
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>