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