incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: Tests failing to run with "mvn clean test" - trunk/server revision 886861
Date Sun, 06 Dec 2009 19:58:14 GMT
Just deployed on Hudson
(http://hudson.zones.apache.org/hudson/job/ESME/35/console) and we
still have the error.

There is a warning regarding the new derby version that could be the
cause of the problem.

[WARNING] POM for 'org.apache.derby:derby:pom:10.5.1.1:compile' is
invalid. It will be ignored for artifact resolution. Reason: Not a
v4.0.0 POM. for project org.apache.derby:derby at
/export/home/hudson/.m2/repository/org/apache/derby/derby/10.5.1.1/derby-10.5.1.1.pom

@Ethan: is the reference in the pom.xml file correct?

D.


On Sun, Dec 6, 2009 at 6:29 PM, Ethan Jewett <esjewett@gmail.com> wrote:
> BTW, in case anyone is interested, I used this blog as my jumping-off
> point into Derby and H2 documentation:
> http://agoncal.wordpress.com/2009/07/05/derby-10-5-1-1-is-really-an-in-memory-database/
>
> Ethan
>
> On Sun, Dec 6, 2009 at 11:27 AM, Ethan Jewett <esjewett@gmail.com> wrote:
>> I've posted a patch to issue 142
>> (https://issues.apache.org/jira/browse/ESME-142).  The patch upgrades
>> the version of Derby we are using in pom.xml and switches the test
>> databases to run in memory.
>>
>> I'm not running H2 because I couldn't figure out immediately how to
>> get Lift to build the DB in H2 properly, so I was getting test
>> failures due to missing tables.
>>
>> Hopefully this will solve the Hudson issue.
>>
>> Ethan
>>
>> On Sun, Dec 6, 2009 at 7:57 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
>>> @Ethan - I'm asuming that is the problem on Hudson. Would be great if
>>> we can solve this.
>>>
>>> Could you take a look and see if you find the maven confíguration to
>>> allow in-memory usage. I looked but didn't find anything.
>>>
>>> On Fri, Dec 4, 2009 at 7:52 PM, Ethan Jewett <esjewett@gmail.com> wrote:
>>>> Would that fix the issue with Hudson as well? I'll look into that a bit.
>>>>
>>>> Ethan
>>>>
>>>> On Fri, Dec 4, 2009 at 12:18 PM, David Pollak
>>>> <feeder.of.the.bears@gmail.com> wrote:
>>>>> On Fri, Dec 4, 2009 at 9:32 AM, Ethan Jewett <esjewett@gmail.com>
wrote:
>>>>>
>>>>>> I'm not following.
>>>>>>
>>>>>> My local repo exactly matched the trunk branch as of when my email
was
>>>>>> sent. I'd deleted my entire local repo and checked out from Apache
SVN
>>>>>> multiple times while trying to debug, so any local changes should
be
>>>>>> fairly well killed off :-)
>>>>>>
>>>>>> It's working fine at the moment for me.
>>>>>>
>>>>>> My concern is why Dick's build & test aren't working. If he can't
>>>>>> build, none of my patches get checked in! ;-)
>>>>>>
>>>>>
>>>>> The problem is likely that the machine he's testing on doesn't grant
>>>>> filesystem write access so the DB can't be accessed.  I'd suggest
>>>>> configuring things for that maven machine to use the in-memory version
of
>>>>> H2.
>>>>>
>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Ethan
>>>>>>
>>>>>> On Fri, Dec 4, 2009 at 11:17 AM, David Pollak
>>>>>> <feeder.of.the.bears@gmail.com> wrote:
>>>>>> > On Fri, Dec 4, 2009 at 5:35 AM, Ethan Jewett <esjewett@gmail.com>
wrote:
>>>>>> >
>>>>>> >> I'm up to date on the latest revision and it seems to be
working fine,
>>>>>> >> at least as far as the tests are concerned.
>>>>>> >>
>>>>>> >
>>>>>> > Ethan,
>>>>>> >
>>>>>> > You have code that is not part of the repo.  Please make sure
you add
>>>>>> > "import net.liftweb.common._" to each of the Scala files and
all will be
>>>>>> > good.
>>>>>> >
>>>>>> > Thanks,
>>>>>> >
>>>>>> > David
>>>>>> >
>>>>>> >
>>>>>> >>
>>>>>> >> Ethan
>>>>>> >>
>>>>>> >> On Thu, Dec 3, 2009 at 5:01 PM, David Pollak
>>>>>> >> <feeder.of.the.bears@gmail.com> wrote:
>>>>>> >> > Fixes are up in the repo
>>>>>> >> >
>>>>>> >> > On Thu, Dec 3, 2009 at 2:15 PM, David Pollak
>>>>>> >> > <feeder.of.the.bears@gmail.com>wrote:
>>>>>> >> >
>>>>>> >> >> Okay,
>>>>>> >> >>
>>>>>> >> >> I reproduced the issue (I guess for some reason
my git svn version of
>>>>>> >> ESME
>>>>>> >> >> is not up to date... sigh).
>>>>>> >> >>
>>>>>> >> >> The issue is exactly as the error indicates.  The
particular line
>>>>>> >> >> (User.scala: 64) is calling S.? outside of a request
context.  This
>>>>>> >> means
>>>>>> >> >> there is no way to tell what the localization string
should be
>>>>>> because
>>>>>> >> there
>>>>>> >> >> is no "S state".  The underlying cause is that
the User is being
>>>>>> created
>>>>>> >> >> outside the scope of an HTTP request.  We need
to do something a tad
>>>>>> >> funky
>>>>>> >> >> with the initialization code.  I'll look into
it.
>>>>>> >> >>
>>>>>> >> >> Thanks,
>>>>>> >> >>
>>>>>> >> >> David
>>>>>> >> >>
>>>>>> >> >>
>>>>>> >> >> On Thu, Dec 3, 2009 at 9:49 AM, Ethan Jewett <esjewett@gmail.com>
>>>>>> >> wrote:
>>>>>> >> >>
>>>>>> >> >>> Hi all,
>>>>>> >> >>>
>>>>>> >> >>> Currently tests are failing to run for me with
a "mvn clean test" in
>>>>>> >> >>> the trunk server on the latest revision (886861).
Can someone
>>>>>> confirm?
>>>>>> >> >>> We can then identify what check-in broke the
build and fix it.
>>>>>> >> >>>
>>>>>> >> >>> Failure is below, which seems to match the
failure occurring in
>>>>>> Hudson.
>>>>>> >> >>>
>>>>>> >> >>> Thanks,
>>>>>> >> >>> Ethan
>>>>>> >> >>>
>>>>>> >> >>>
>>>>>> >> >>>
>>>>>> >> >>> 2009-12-03 12:45:51.137:INFO::Started SocketConnector@0.0.0.0:8989
>>>>>> >> >>> org.apache.maven.surefire.booter.SurefireExecutionException:
null;
>>>>>> >> >>> nested exception is java.lang.ExceptionInInitializerError:
null
>>>>>> >> >>> java.lang.ExceptionInInitializerError
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> org.apache.esme.lib.MsgParserSpecsAsTest.<init>(MsgParseTest.scala:45)
>>>>>> >> >>>        at
>>>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>>>>> >> >>> Method)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>>>>> >> >>>        at
>>>>>> >> java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>>>>>> >> >>>        at java.lang.Class.newInstance0(Class.java:355)
>>>>>> >> >>>        at java.lang.Class.newInstance(Class.java:308)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> org.specs.runner.JUnitSuiteRunner.testSuite(JUnitSuiteRunner.scala:37)
>>>>>> >> >>>        at
>>>>>> >> org.specs.runner.JUnitSuiteRunner.run(JUnitSuiteRunner.scala:45)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
>>>>>> >> >>>        at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
>>>>>> >> >>>        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.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
>>>>>> >> >>> Caused by: java.lang.IllegalStateException:
Attempted to use
>>>>>> resource
>>>>>> >> >>> bundles outside of an initialized S scope.
S only usable when
>>>>>> >> >>> initialized, such as during request processing.
Did you call S.?
>>>>>> from
>>>>>> >> >>> Boot?
>>>>>> >> >>>        at net.liftweb.http.S$.resourceBundles(S.scala:611)
>>>>>> >> >>>        at net.liftweb.http.S$.$qmark(S.scala:637)
>>>>>> >> >>>        at net.liftweb.http.S$.$qmark(S.scala:655)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> org.apache.esme.model.User$.org$apache$esme$model$User$$profileChanged(User.scala:64)
>>>>>> >> >>>        at org.apache.esme.model.User$$anonfun$1.apply(User.scala:50)
>>>>>> >> >>>        at org.apache.esme.model.User$$anonfun$1.apply(User.scala:50)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> net.liftweb.mapper.MetaMapper$$anonfun$eachField$2.apply(MetaMapper.scala:1177)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> >>
>>>>>> net.liftweb.mapper.MetaMapper$$anonfun$eachField$2.apply(MetaMapper.scala:1177)
>>>>>> >> >>>        at scala.List.foreach(List.scala:841)
>>>>>> >> >>>        at
>>>>>> >> >>> net.liftweb.mapper.MetaMapper$class.eachField(MetaMapper.scala:1177)
>>>>>> >> >>>        at net.liftweb.mapper.MetaMapper$class.net
>>>>>> >> >>> $liftweb$mapper$MetaMapper$$_afterSave(MetaMapper.scala:1190)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> net.liftweb.mapper.MetaMapper$$anonfun$15.apply(MetaMapper.scala:706)
>>>>>> >> >>>        at
>>>>>> >> >>>
>>>>>> net.liftweb.mapper.MetaMapper$$anonfun$15.apply(MetaMapper.scala:643)
>>>>>> >> >>>        at net.liftweb.mapper.DB$$anonfun$use$1.apply(DB.scala:424)
>>>>>> >> >>>        at net.liftweb.util.DynoVar$class.run(ThreadGlobal.scala:91)
>>>>>> >> >>>        at net.liftweb.mapper.DB$currentConn$.run(DB.scala:411)
>>>>>> >> >>>        at net.liftweb.mapper.DB$.use(DB.scala:421)
>>>>>> >> >>>        at
>>>>>> >> net.liftweb.mapper.MetaMapper$class.save(MetaMapper.scala:642)
>>>>>> >> >>>        at org.apache.esme.model.User$.save(User.scala:49)
>>>>>> >> >>>        at
>>>>>> >> net.liftweb.mapper.Mapper$$anonfun$save$1.apply(Mapper.scala:88)
>>>>>> >> >>>        at
>>>>>> >> net.liftweb.mapper.Mapper$$anonfun$save$1.apply(Mapper.scala:88)
>>>>>> >> >>>        at
>>>>>> net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:67)
>>>>>> >> >>>        at net.liftweb.mapper.Safe$.runSafe(Safe.scala:44)
>>>>>> >> >>>        at net.liftweb.mapper.Mapper$class.runSafe(Mapper.scala:54)
>>>>>> >> >>>        at org.apache.esme.model.User.runSafe(User.scala:181)
>>>>>> >> >>>        at net.liftweb.mapper.Mapper$class.save(Mapper.scala:87)
>>>>>> >> >>>        at org.apache.esme.model.User.save(User.scala:181)
>>>>>> >> >>>        at
>>>>>> org.apache.esme.JettyTestServer$.start(JettySetup.scala:65)
>>>>>> >> >>>        at
>>>>>> >> >>> org.apache.esme.lib.MsgParserSpecs$.<init>(MsgParseTest.scala:49)
>>>>>> >> >>>        at
>>>>>> >> org.apache.esme.lib.MsgParserSpecs$.<clinit>(MsgParseTest.scala)
>>>>>> >> >>>        ... 19 more
>>>>>> >> >>> [ERROR] There are test failures.
>>>>>> >> >>>
>>>>>> >> >>
>>>>>> >> >>
>>>>>> >> >>
>>>>>> >> >> --
>>>>>> >> >> Lift, the simply functional web framework http://liftweb.net
>>>>>> >> >> Beginning Scala http://www.apress.com/book/view/1430219890
>>>>>> >> >> Follow me: http://twitter.com/dpp
>>>>>> >> >> Surf the harmonics
>>>>>> >> >>
>>>>>> >> >
>>>>>> >> >
>>>>>> >> >
>>>>>> >> > --
>>>>>> >> > Lift, the simply functional web framework http://liftweb.net
>>>>>> >> > Beginning Scala http://www.apress.com/book/view/1430219890
>>>>>> >> > Follow me: http://twitter.com/dpp
>>>>>> >> > Surf the harmonics
>>>>>> >> >
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > Lift, the simply functional web framework http://liftweb.net
>>>>>> > Beginning Scala http://www.apress.com/book/view/1430219890
>>>>>> > Follow me: http://twitter.com/dpp
>>>>>> > Surf the harmonics
>>>>>> >
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lift, the simply functional web framework http://liftweb.net
>>>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>>>> Follow me: http://twitter.com/dpp
>>>>> Surf the harmonics
>>>>>
>>>>
>>>
>>
>

Mime
View raw message