Scaladoc exception on build...

Partest output has been improved in the last commit and should now print
the log in the event that an exception is thrown in the test.

In your build, you could maybe take a look at the log file that was
produced in test/scaladoc/model. That could give more insight into what
caused the error.

There is a possibility that the error occurs due to ant running out of
permgen space, which threw an OutOfMemoryError. I've been observing this
lately when the permgen size is set to 64mb.

On 08/10/10 01:26, Derek Chen-Becker wrote:
> I'm trying to do a full build before checking in a fix for #3605, but
> when it gets to the test.scaladoc target it fails. As far as I know I
> didn't touch anything scaladoc related, so I'm wondering if something on
> my machine is broken or if there's actually a broken build checked in.
> I'm running "ant all.clean test" and this is what it eventually prints:
>
> ...
> [partest] testing: [...]/files/continuations-run/trycatch1.scala
> [ OK ]
> [partest] testing: [...]/files/continuations-run/while0.scala
> [ OK ]
> [partest] testing: [...]/files/continuations-run/while1.scala
> [ OK ]
> [partest] testing: [...]/files/continuations-run/while2.scala
> [ OK ]
> [partest] Test suite finished with no failures.
>
> test.scaladoc:
> [partest] Running scalacheck tests
> [partest] testing: [...]/scaladoc/model/CommentFactoryTest.scala
> [FAILED]
>
> BUILD FAILED
> /home/software/scalastuff/scalasvn/build.xml:1596:
> java.lang.RuntimeException: Test suite finished with 1 case failing:
> /home/software/scalastuff/scalasvn/test/scaladoc/model/CommentFactoryTest.scala
> [FAILED]
> at scala.Predef$.error(Predef.scala:58)
> at
> scala.tools.partest.PartestTask$$anonfun$f$1$1.apply(PartestTask.scala:265)
> at
> scala.tools.partest.PartestTask$$anonfun$f$1$1.apply(PartestTask.scala:265)
> at scala.tools.partest.PartestTask.execute(PartestTask.scala:274)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> 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.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1360)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1329)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1212)
> at org.apache.tools.ant.Main.runBuild(Main.java:801)
> at org.apache.tools.ant.Main.startAnt(Main.java:218)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>
> Thanks,
>
> Derek
> .
>
>

On 10/08/2010 08:43 AM, Aleksandar Prokopec wrote:
> Partest output has been improved in the last commit and should now print
> the log in the event that an exception is thrown in the test.
>
> In your build, you could maybe take a look at the log file that was
> produced in test/scaladoc/model. That could give more insight into what
> caused the error.
>
> There is a possibility that the error occurs due to ant running out of
> permgen space, which threw an OutOfMemoryError. I've been observing this
> lately when the permgen size is set to 64mb.

I checked the log
(test/scaladoc/model/CommentFactoryTest-scalacheck.log) and it's a zero
byte file. FWIW, the ANT options are:

[echo] Using ANT_OPTS: -Xms1536M -Xmx1536M -Xss1M -XX:MaxPermSize=192M
-XX:+UseParallelGC

So it looks like I'm allowing the JVM to use up to 192M for the perm space.

Derek

> I checked the log
> (test/scaladoc/model/CommentFactoryTest-scalacheck.log) and it's a zero
> byte file.

Does this still occur even when you update to the newest revision?

> FWIW, the ANT options are:
>
> [echo] Using ANT_OPTS: -Xms1536M -Xmx1536M -Xss1M -XX:MaxPermSize=192M
> -XX:+UseParallelGC
>
> So it looks like I'm allowing the JVM to use up to 192M for the perm space.
>
>

That's what I thought originally as well. But, upon closer inspection
with VisualVM to see what the permgen size really is, this turned out
not to be true - although ant wrote this out. Even when I first do:

> echo $ANT_OPTS

and get an empty echo, the permgen size remains app. 64mb.

This is in my case, at least.

Alex

4CAF53E3 [dot] 1000404 [at] epfl [dot] ch" type="cite">That's what I thought originally as well. But, upon closer inspection with VisualVM to see what the permgen size really is, this turned out not to be true - although ant wrote this out. Even when I first do:

> echo $ANT_OPTS

On 10/08/2010 11:49 AM, Aleksandar Prokopec wrote:
> btw, I then did:
>
> $ export ANT_OPTS=-XX:MaxPermSize=192m
>
> and it worked.

OK, that seems to have fixed it. Strange...

Derek