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
>>>>