I can again see some test failure for gfac-core. Can someone please look into 
this?


[main] INFO  impl.PropertiesBasedServiceImpl  - 
Scheduler:org.apache.airavata.core.gfac.scheduler.impl.SchedulerImpl is loaded
java.lang.NullPointerException
        at 
org.apache.airavata.core.gfac.scheduler.impl.SchedulerImpl.schedule(SchedulerImpl.java:51)
        at 
org.apache.airavata.core.gfac.services.impl.AbstractSimpleService.execute(AbstractSimpleService.java:58)
        at 
org.apache.airavata.core.gfac.services.impl.PropertiesBasedServiceImplTest.testExecute(PropertiesBasedServiceImplTest.java:140)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
        at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
        at $Proxy0.invoke(Unknown Source)
        at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
        at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
        at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.765 sec <<< 
FAILURE!

Thanks
Raminder

On Aug 19, 2011, at 4:16 PM, Heshan Suriyaarachchi wrote:

> On Fri, Aug 19, 2011 at 3:56 PM, Lahiru Gunathilake <[email protected]>wrote:
> 
>> Fixed the issue ! Please take an svn update in gfac-core and build again !
>> 
> Now all the tests pass without an issue.
> 
> Thanks
> 
>> 
>> Thanks Heshan for pointing this out.
>> 
>> Regards
>> Lahiru
>> 
>> On Fri, Aug 19, 2011 at 3:50 PM, Lahiru Gunathilake <[email protected]
>>> wrote:
>> 
>>> Hi Patnachai,
>>> 
>>> We need to commit this default setup in to SVN which will fix the build
>>> error. Later on when users configure the setup we can provide a document
>> how
>>> to edit the service.properties file.
>>> 
>>> Regards
>>> Lahiru
>>> 
>>> 
>>> On Fri, Aug 19, 2011 at 3:43 PM, [email protected] <
>>> [email protected]> wrote:
>>> 
>>>> Hello Heshan,
>>>> 
>>>> Thank you for interesting in Airavata.
>>>> 
>>>> Yes, you need to setup jackrabbit on your machine to pass the test at
>> the
>>>> current code.
>>>> However, the default configuration for test cases should use in-memory
>>>> database instead of persistent one.
>>>> 
>>>> Could you submit a JIRA ticket for the issue?
>>>> 
>>>> For workaround without a jackrabbit binary, you need to change
>>>> modules/gfac-core/src/test/resources/service.properties from
>>>> airavata/trunk.
>>>> 
>>>> comment these 2 lines:
>>>> 
>>>> jcr.class=org.apache.jackrabbit.rmi.repository.RmiRepositoryFactory
>>>> org.apache.jackrabbit.repository.uri=http://localhost:8080/rmi
>>>> 
>>>> and uncomment this line:
>>>> #jcr.class=org.apache.jackrabbit.core.RepositoryFactoryImpl
>>>> 
>>>> On Fri, Aug 19, 2011 at 3:34 PM, Heshan Suriyaarachchi <
>>>> [email protected]> wrote:
>>>> 
>>>>> Hi Devs,
>>>>> 
>>>>> I checked out and built the Airavata trunk successfully without tests.
>>>> But
>>>>> when I ran the build with tests, I can see test failures. I am getting
>> a
>>>>> test failure in
>>>>> 
>>>> 
>> org.apache.airavata.core.gfac.services.impl.PropertiesBasedServiceImplTest.
>>>>> 
>>>>> I had a look at the test and I'm guessing I need to setup jackrabbit
>> in
>>>> my
>>>>> machine inorder for this test to be successful. I am new to this
>> project
>>>>> and
>>>>> please correct me if I am wrong.
>>>>> 
>>>>> If so what are the other third party projects that is used by
>> airavata?
>>>> It
>>>>> will help me to set them up locally and see.
>>>>> 
>>>>> --
>>>>> Regards,
>>>>> Heshan Suriyaarachchi
>>>>> 
>>>>> http://heshans.blogspot.com/
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Best Regards,
>>>> Patanachai Tangchaisin
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> System Analyst Programmer
>>> PTI Lab
>>> Indiana University
>>> 
>>> 
>> 
>> 
>> --
>> System Analyst Programmer
>> PTI Lab
>> Indiana University
>> 
> 
> 
> 
> -- 
> Regards,
> Heshan Suriyaarachchi
> 
> http://heshans.blogspot.com/

Reply via email to