You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by David Saff <da...@saff.net> on 2009/05/05 15:57:47 UTC
Fwd: [GUMP@vmgump]: Project test-junit (in module junit) failed
Does Gump do anything odd with threads in tests? It seems that any
test that contains a timeout ends up failing in Gump, but they're very
useful for our development, and no other environment seems to have a
problem with it. Thanks,
David Saff
---------- Forwarded message ----------
From: Gump Integration <ge...@gump.apache.org>
Date: Tue, May 5, 2009 at 4:27 AM
Subject: [GUMP@vmgump]: Project test-junit (in module junit) failed
To: David Saff <sa...@mit.edu>
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project test-junit has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 219 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- test-junit : Java Unit test framework
Full details are available at:
http://vmgump.apache.org/gump/public/junit/test-junit/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages)
were provided:
-INFO- Failed with reason build failed
The following work was performed:
http://vmgump.apache.org/gump/public/junit/test-junit/gump_work/build_junit_test-junit.html
Work Name: build_junit_test-junit (Type: Build)
Work ended in a state of : Failed
Elapsed: 34 secs
Command Line: /usr/lib/jvm/java-6-sun/bin/java
-Djava.awt.headless=true
-Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
org.apache.tools.ant.Main
-Dgump.merge=/srv/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only -Ddist=gump-test
[Working Directory: /srv/gump/public/workspace/junit]
CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/junit/lib/hamcrest-core-1.1.jar:/srv/gump/public/workspace/junit/target/test/java:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/junit/dist/junit-05052009.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
---------------------------------------------
[java] JUnit version 4.7-SNAPSHOT-20090507-1339
[java] ............................................................................................................................................................................................................................................................................................I.I.......................................................................................................................................................E
[java] Time: 23.551
[java] There was 1 failure:
[java] 1) globalTimeoutAvoidsInfiniteLoop(org.junit.tests.experimental.TimeoutInterceptorTest)
[java] java.lang.Exception: test timed out after 100 milliseconds
[java] at java.lang.Thread.dumpThreads(Native Method)
[java] at java.lang.Thread.getStackTrace(Thread.java:1423)
[java] at
org.junit.internal.runners.statements.FailOnTimeout.evaluate(FailOnTimeout.java:43)
[java] at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
[java] at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
[java] at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
[java] at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:44)
[java] at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:202)
[java] at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
[java] at
org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:195)
[java] at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
[java] at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
[java] at org.junit.runners.ParentRunner.run(ParentRunner.java:242)
[java] at org.junit.runners.Suite.runChild(Suite.java:119)
[java] at org.junit.runners.Suite.runChild(Suite.java:25)
[java] at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:202)
[java] at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
[java] at
org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:195)
[java] at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
[java] at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
[java] at org.junit.runners.ParentRunner.run(ParentRunner.java:242)
[java] at org.junit.runner.JUnitCore.run(JUnitCore.java:159)
[java] at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
[java] at org.junit.runner.JUnitCore.run(JUnitCore.java:129)
[java] at org.junit.runner.JUnitCore.runClasses(JUnitCore.java:77)
[java] at
org.junit.tests.experimental.TimeoutInterceptorTest.globalTimeoutAvoidsInfiniteLoop(TimeoutInterceptorTest.java:35)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
[java] at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
[java] at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
[java] at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
[java] at
org.junit.internal.runners.statements.FailOnTimeout$1.run(FailOnTimeout.java:28)
[java]
[java] FAILURES!!!
[java] Tests run: 436, Failures: 1
[java]
BUILD FAILED
/srv/gump/public/workspace/junit/build.xml:142: Java returned: 1
Total time: 33 seconds
---------------------------------------------
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/junit/test-junit/rss.xml
- Atom: http://vmgump.apache.org/gump/public/junit/test-junit/atom.xml
============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 06000005052009, vmgump:vmgump-public:06000005052009
Gump E-mail Identifier (unique within run) #20.
--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fwd: [GUMP@vmgump]: Project test-junit (in module junit) failed
Posted by Stefan Bodewig <bo...@apache.org>.
On 2009-05-05, David Saff <da...@saff.net> wrote:
> Are ours the only performance tests in Gump?
Possible, I'm not aware of explicit performance tests. I do know that
the Ant testsuite had to increase some Thread.sleep() values in order
to make all tests pass.
> Should we create a gump-only suite?
Your choice, really. If it is of any value to run the tests inside
Gump than increasing timeouts may be a good way ro deal with it -
otherwise it may make sense to disable them.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fwd: [GUMP@vmgump]: Project test-junit (in module junit) failed
Posted by David Saff <da...@saff.net>.
Are ours the only performance tests in Gump? Should we create a
gump-only suite?
David
On Tue, May 5, 2009 at 10:15 AM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2009-05-05, David Saff <da...@saff.net> wrote:
>
>> Does Gump do anything odd with threads in tests?
>
> No.
>
>> It seems that any test that contains a timeout ends up failing in
>> Gump, but they're very useful for our development, and no other
>> environment seems to have a problem with it.
>
> It may very well be that vmgump is a lot slower than any of your test
> environments since it usually is on heavy I/O load (performing SCM
> updates in parallel to running builds).
>
> The tests seem to pass on our Solaris zone
> <http://gump.zones.apache.org/gump/test/junit/test-junit/index.html>,
> for example.
>
> Stefan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fwd: [GUMP@vmgump]: Project test-junit (in module junit) failed
Posted by Stefan Bodewig <bo...@apache.org>.
On 2009-05-05, David Saff <da...@saff.net> wrote:
> Does Gump do anything odd with threads in tests?
No.
> It seems that any test that contains a timeout ends up failing in
> Gump, but they're very useful for our development, and no other
> environment seems to have a problem with it.
It may very well be that vmgump is a lot slower than any of your test
environments since it usually is on heavy I/O load (performing SCM
updates in parallel to running builds).
The tests seem to pass on our Solaris zone
<http://gump.zones.apache.org/gump/test/junit/test-junit/index.html>,
for example.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org