Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
On Wed, Oct 10, 2012 at 12:38 PM, Gump Integration Build
bode...@apache.org wrote:
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 gene...@gump.apache.org.
Project test-ant-no-xerces has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 128 runs.
FYI: XMLResultAggregatorTest and archives-test failures:
[junit] Testsuite:
org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregatorTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.192 sec
[junit]
[junit] Testcase:
testFrames(org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregatorTest):
Caused
an ERROR
[junit] Errors while applying transformations: Fatal error during
transformation
[junit] Errors while applying transformations: Fatal error during
transformation
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.transform(AggregateTransformer.java:267)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregator.execute(XMLResultAggregator.java:158)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregatorTest.testFrames(XMLResultAggregatorTest.java:82)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[junit] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[junit] at java.lang.reflect.Method.invoke(Method.java:601)
[junit] at junit.framework.TestCase.runTest(TestCase.java:176)
[junit] at junit.framework.TestCase.runBare(TestCase.java:141)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:122)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:142)
[junit] at junit.framework.TestResult.run(TestResult.java:125)
[junit] at junit.framework.TestCase.run(TestCase.java:129)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:255)
[junit] at junit.framework.TestSuite.run(TestSuite.java:250)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:520)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1060)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:884)
[junit] Caused by: Fatal error during transformation
[junit] at
org.apache.tools.ant.taskdefs.XSLTProcess.handleTransformationError(XSLTProcess.java:1271)
[junit] at
org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:860)
[junit] at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:388)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.transform(AggregateTransformer.java:265)
[junit] ... 17 more
[junit] Caused by: Fatal error during transformation
[junit] at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.fatalError(TraXLiaison.java:531)
[junit] at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:895)
[junit] at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.readTemplates(TraXLiaison.java:300)
[junit] at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.createTransformer(TraXLiaison.java:317)
[junit] at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:178)
[junit] at
org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:850)
[junit] ... 19 more
[junit] Caused by:
javax.xml.transform.TransformerConfigurationException: Could not
compile stylesheet
[junit] at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:885)
[junit] ... 23 more
[junit]
[junit]
[junit] TEST
org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregatorTest
FAILED
[au:antunit] Build File:
/srv/gump/public/workspace/ant/src/tests/antunit/types/resources/archives-test.xml
[au:antunit] Tests run: 5, Failures: 0, Errors: 3, Time elapsed: 0.197 sec
[au:antunit] Target: testCircularReference took 0.001 sec
[au:antunit] Target: testMixingZipsAndTars caused an ERROR
[au:antunit]at line 43, column 29
[au:antunit]Message:
/srv/gump/public/workspace/ant/src/tests/antunit/types/resources/${ant.home}/lib
does not exist.
[au:antunit]took 0.004 sec
[au:antunit] Target: testReference caused an ERROR
[au:antunit]at line 70, column 29
[au:antunit]Message:
/srv/gump/public/workspace/ant/src/tests/antunit/types/resources/${ant.home}/lib
does not exist.
[au:antunit]took 0.002 sec
[au:antunit] Target: testExtractJars caused an
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
Any idea (Stefan?) how or why ${ant.home} shows up in the middle of
the messages for the tests in
src/tests/antunit/types/resources/archives-test.xml ?
Matt
On Tue, Sep 4, 2012 at 3:12 AM, Gump Integration Build
bode...@apache.org wrote:
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 gene...@gump.apache.org.
Project test-ant-no-xerces has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 58 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- test-ant-no-xerces : Java based build tool
Full details are available at:
http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-INFO- Optional dependency rhino prerequisite failed with reason build failed
-INFO- Optional dependency jakarta-tomcat-4.0 prerequisite failed with
reason build failed
-INFO- Failed with reason build failed
The following work was performed:
http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/gump_work/build_ant_test-ant-no-xerces.html
Work Name: build_ant_test-ant-no-xerces (Type: Build)
Work ended in a state of : Failed
Elapsed: 16 mins 52 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true
-Dbuild.sysclasspath=only org.apache.tools.ant.Main
-Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dtest.haltonfailure=false
-Dant.home=/srv/gump/public/workspace/ant/dist run-tests
[Working Directory: /srv/gump/public/workspace/ant]
CLASSPATH:
/usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/build/testcases:/srv/gump/public/workspace/ant/src/tests/junit:/srv/gump/public/workspace/ant/src/etc/testcases:/srv/gump/public/workspace/ant/src/etc/testcases/taskdefs/optional/out:/srv/gump/public/workspace/ant/src/tests/antunit/filters:/srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/importtests:/srv/gump/public/workspace/ant/src/tests/antunit/filters/foo:/srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/foo:/srv/gump/public/workspace/ant/build/antunit/tmp/testinput/build:/srv/gump/public/workspace/ant/build/antunit/tmp/testoutput:/srv/gump/public/workspace/ant/build/antunit/tmp/test.jar:/srv/gump/public/workspace/ant/build/antunit/tmp/test1.jar:/srv/gump/public/workspace/ant/build/antunit/tmp/test2.jar:/srv/gump/public/workspace/ant/build/antunit/tmp/test3.jar:/srv/gump/public/workspace/ant/build/antunit/tmp/test4.jar:/srv/gump/public/workspace/ant/build/antunit/tmp/test5.
jar:/srv/gump/public/workspace/ant/build/antunit/tmp/resources:/srv/gump/public/workspace/ant/build/lib/ant.jar:/srv/gump/public/workspace/ant/build/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/build/lib/ant-antlr.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bsf.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-log4j.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-oro.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-regexp.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-logging.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-net.jar:/srv/gump/public/workspace/ant/build/lib/ant-jai.jar:/srv/gump/public/workspace/ant/build/lib/ant-javamail.jar:/srv/gump/public/workspace/ant/build/lib/ant-jdepend.jar:/srv/gump/public/workspace/ant/build
/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/build/lib/ant-jsch.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/build/lib/ant-swing.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/apache-commons/bcel/target/bcel-6.0-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-04092012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-04092012.jar:/srv/gump/public/workspace/apache-commons/net/target/commons-net-3.2-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/net/target/commons-net-ftp-3.2-SNAPSHOT.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/public/workspace/jakarta-bsf/build/lib/bsf.jar:/srv/gump/packages/apache-attic/jakarta-regexp-1.5.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
Le 28 avr. 2011 à 21:39, Nicolas Lalevée a écrit : Le 28 avr. 2011 à 00:39, Matt Benson a écrit : 2011/4/27 Nicolas Lalevée nicolas.lale...@hibnet.org: I could only reproduce the apply-test failing locally (on a mac). The following command line got me more info about what's happening: ant -lib lib/optional/ant-antunit-1.1.jar antunit-report -Dantunit.testcase=taskdefs/exec/apply-test.xml -Dantunit.loglevel=info In the output I can see these lines: [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] z after y after blah [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] x after y after blah Not sure what to conclude from that since I'm not yet familiar with what LeadPipeInputStream does. At a first glance I would say that we could interpret that if the pipe is broken, then the writing Thread is no longer alive, which would be basically be a nominal case and not an error one ? If it helps, LeadPipeInputStream (a poor pun) is intended to replace the java.io.PipedInputStream to recover from writing thread is no longer alive errors, because often there is data remaining to be read when the writer has already sent all he had to send, then terminated. ok I see. Then I think it will make sense to handle the Pipe broken just like the Write end dead. The read method in PipedInputStream start to check the thread status, and can fail with a IOE with Write end dead as a message the write thread is dead. If the write thread are still alive but no content is yet available, a loop begins to wait for content. Then if at some point there's still no content to read but the write thread has stopped, there is an IOE with Pipe broken as a message. So having either Pipe broken or Write end dead is just a matter of timing. I'll commit a fix. Tested locally the ant unit tests then works (tested several times). And I think it will fix the bug #48789 [1]. If gump shows us it now works I'll update the what's new and close #48789. If not I'll revert my commit. gump seems happier, bug closed as resolved. One test still failing, I haven't looked at it: [au:antunit] Target: test-redirector-input-output-inputencoding-outputencoding FAILED [au:antunit]at line 552, column 24 [au:antunit]Message: Assertion failed [au:antunit]took 1.424 sec Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
2011/4/29 Nicolas Lalevée nicolas.lale...@hibnet.org: Le 28 avr. 2011 à 21:39, Nicolas Lalevée a écrit : Le 28 avr. 2011 à 00:39, Matt Benson a écrit : 2011/4/27 Nicolas Lalevée nicolas.lale...@hibnet.org: I could only reproduce the apply-test failing locally (on a mac). The following command line got me more info about what's happening: ant -lib lib/optional/ant-antunit-1.1.jar antunit-report -Dantunit.testcase=taskdefs/exec/apply-test.xml -Dantunit.loglevel=info In the output I can see these lines: [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] z after y after blah [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] x after y after blah Not sure what to conclude from that since I'm not yet familiar with what LeadPipeInputStream does. At a first glance I would say that we could interpret that if the pipe is broken, then the writing Thread is no longer alive, which would be basically be a nominal case and not an error one ? If it helps, LeadPipeInputStream (a poor pun) is intended to replace the java.io.PipedInputStream to recover from writing thread is no longer alive errors, because often there is data remaining to be read when the writer has already sent all he had to send, then terminated. ok I see. Then I think it will make sense to handle the Pipe broken just like the Write end dead. The read method in PipedInputStream start to check the thread status, and can fail with a IOE with Write end dead as a message the write thread is dead. If the write thread are still alive but no content is yet available, a loop begins to wait for content. Then if at some point there's still no content to read but the write thread has stopped, there is an IOE with Pipe broken as a message. So having either Pipe broken or Write end dead is just a matter of timing. I'll commit a fix. Tested locally the ant unit tests then works (tested several times). And I think it will fix the bug #48789 [1]. If gump shows us it now works I'll update the what's new and close #48789. If not I'll revert my commit. gump seems happier, bug closed as resolved. Thanks for your attention to this, Nicolas. Matt One test still failing, I haven't looked at it: [au:antunit] Target: test-redirector-input-output-inputencoding-outputencoding FAILED [au:antunit] at line 552, column 24 [au:antunit] Message: Assertion failed [au:antunit] took 1.424 sec Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
Le 28 avr. 2011 à 00:39, Matt Benson a écrit : 2011/4/27 Nicolas Lalevée nicolas.lale...@hibnet.org: I could only reproduce the apply-test failing locally (on a mac). The following command line got me more info about what's happening: ant -lib lib/optional/ant-antunit-1.1.jar antunit-report -Dantunit.testcase=taskdefs/exec/apply-test.xml -Dantunit.loglevel=info In the output I can see these lines: [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] z after y after blah [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] x after y after blah Not sure what to conclude from that since I'm not yet familiar with what LeadPipeInputStream does. At a first glance I would say that we could interpret that if the pipe is broken, then the writing Thread is no longer alive, which would be basically be a nominal case and not an error one ? If it helps, LeadPipeInputStream (a poor pun) is intended to replace the java.io.PipedInputStream to recover from writing thread is no longer alive errors, because often there is data remaining to be read when the writer has already sent all he had to send, then terminated. ok I see. Then I think it will make sense to handle the Pipe broken just like the Write end dead. The read method in PipedInputStream start to check the thread status, and can fail with a IOE with Write end dead as a message the write thread is dead. If the write thread are still alive but no content is yet available, a loop begins to wait for content. Then if at some point there's still no content to read but the write thread has stopped, there is an IOE with Pipe broken as a message. So having either Pipe broken or Write end dead is just a matter of timing. I'll commit a fix. Tested locally the ant unit tests then works (tested several times). And I think it will fix the bug #48789 [1]. If gump shows us it now works I'll update the what's new and close #48789. If not I'll revert my commit. Nicolas [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=48789 - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
I could only reproduce the apply-test failing locally (on a mac). The following command line got me more info about what's happening: ant -lib lib/optional/ant-antunit-1.1.jar antunit-report -Dantunit.testcase=taskdefs/exec/apply-test.xml -Dantunit.loglevel=info In the output I can see these lines: [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] z after y after blah [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] x after y after blah Not sure what to conclude from that since I'm not yet familiar with what LeadPipeInputStream does. At a first glance I would say that we could interpret that if the pipe is broken, then the writing Thread is no longer alive, which would be basically be a nominal case and not an error one ? Nicolas Le 23 avr. 2011 à 22:48, Antoine Levy Lambert a écrit : We currently have two antunit tests failing in gump. I am looking into this, I am trying my luck at installing virtualbox on my MacBook. Regards, Antoine [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/exec/exec-test.xml [au:antunit] Tests run: 30, Failures: 1, Errors: 0, Time elapsed: 32.748 sec [au:antunit] Target: test-redirector-input-output-inputencoding-outputencoding FAILED [au:antunit] at line 552, column 24 [au:antunit] Message: Assertion failed [au:antunit] took 1.428 sec [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/exec/apply-test.xml [au:antunit] Tests run: 30, Failures: 1, Errors: 0, Time elapsed: 98.754 sec [au:antunit] Target: testRedirector14 FAILED [au:antunit] at line 611, column 76 [au:antunit] Message: Expected log to contain 'z after y after blahx after y after blah' at level info [au:antunit] took 3.269 sec On 4/23/11 8:27 AM, Gump Integration Build wrote: Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/index.html - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
2011/4/27 Nicolas Lalevée nicolas.lale...@hibnet.org: I could only reproduce the apply-test failing locally (on a mac). The following command line got me more info about what's happening: ant -lib lib/optional/ant-antunit-1.1.jar antunit-report -Dantunit.testcase=taskdefs/exec/apply-test.xml -Dantunit.loglevel=info In the output I can see these lines: [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] z after y after blah [au:antunit] error at LeadPipeInputStream.read(): Pipe broken [au:antunit] x after y after blah Not sure what to conclude from that since I'm not yet familiar with what LeadPipeInputStream does. At a first glance I would say that we could interpret that if the pipe is broken, then the writing Thread is no longer alive, which would be basically be a nominal case and not an error one ? If it helps, LeadPipeInputStream (a poor pun) is intended to replace the java.io.PipedInputStream to recover from writing thread is no longer alive errors, because often there is data remaining to be read when the writer has already sent all he had to send, then terminated. Matt Nicolas Le 23 avr. 2011 à 22:48, Antoine Levy Lambert a écrit : We currently have two antunit tests failing in gump. I am looking into this, I am trying my luck at installing virtualbox on my MacBook. Regards, Antoine [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/exec/exec-test.xml [au:antunit] Tests run: 30, Failures: 1, Errors: 0, Time elapsed: 32.748 sec [au:antunit] Target: test-redirector-input-output-inputencoding-outputencoding FAILED [au:antunit] at line 552, column 24 [au:antunit] Message: Assertion failed [au:antunit] took 1.428 sec [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/exec/apply-test.xml [au:antunit] Tests run: 30, Failures: 1, Errors: 0, Time elapsed: 98.754 sec [au:antunit] Target: testRedirector14 FAILED [au:antunit] at line 611, column 76 [au:antunit] Message: Expected log to contain 'z after y after blahx after y after blah' at level info [au:antunit] took 3.269 sec On 4/23/11 8:27 AM, Gump Integration Build wrote: Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/index.html - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
We currently have two antunit tests failing in gump. I am looking into this, I am trying my luck at installing virtualbox on my MacBook. Regards, Antoine [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/exec/exec-test.xml [au:antunit] Tests run: 30, Failures: 1, Errors: 0, Time elapsed: 32.748 sec [au:antunit] Target: test-redirector-input-output-inputencoding-outputencoding FAILED [au:antunit] at line 552, column 24 [au:antunit] Message: Assertion failed [au:antunit] took 1.428 sec [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/exec/apply-test.xml [au:antunit] Tests run: 30, Failures: 1, Errors: 0, Time elapsed: 98.754 sec [au:antunit] Target: testRedirector14 FAILED [au:antunit] at line 611, column 76 [au:antunit] Message: Expected log to contain 'z after y after blahx after y after blah' at level info [au:antunit] took 3.269 sec On 4/23/11 8:27 AM, Gump Integration Build wrote: Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/index.html - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
Hi, any idea why we are seeing these gump failures : BUILD FAILED /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/import-test.xml:42: Cannot find override.xml imported from /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/import-test.xml ? Antoine On 1/31/2011 1:09 PM, Gump Integration Build wrote: To whom it may engage... Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/index.html - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
Hi, this is a new test for *Bug 50515* https://issues.apache.org/bugzilla/show_bug.cgi?id=50515 - Different result for chinese encoding of propertyfile task which is failing like that (see below). It should not be failing any more in the next gump run. Gump updated ant sometime between the addition of the test and the check in of the fix. Regards, Antoine [au:antunit] Build File: /srv/gump/public/workspace/ant/src/tests/antunit/taskdefs/propertyfile-test.xml [au:antunit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.009 sec [au:antunit] Target: testInternationalText FAILED [au:antunit]at line 38, column 43 [au:antunit]Message: è?¬ å^© é£Y å? æ0/00¹ ç^(TM)¼ å...¬ å?¸ [au:antunit]took 0.005 sec Regards, Antoine On 1/4/11 12:43 AM, Gump Integration Build wrote: 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 gene...@gump.apache.org. Project test-ant-no-xerces has an issue affecting its community integration. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
Apart from some scriptef tests that are failing because rhino didn't build we also have a few test failures in the redirector tests. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [GUMP@vmgump]: Project test-ant-no-xerces (in module ant) failed
The test failure is related to a difference between Xalan and the version of Xalan that is part of Java5 (and Java6 as well). When ASF Xalan encounters an invalid XML file, it informs the registered ErrorListener via fatalError and our implementation of the ErrorListener turns it into a BuildException. The JDK Xalan either doesn't invoke fatalError at all or ignores our BuildException and throws the original TransformerException - no matter what, either violates my reading of the JAXP 1.3 javadocs of ErrorListener: , | For transformation errors, a Transformer must use this interface | instead of throwing an exception: it is up to the application to | decide whether to throw an exception for different types of errors and | warnings. Note however that the Transformer is not required to | continue with the transformation after a call to fatalError. ` but I guess it is the next paragraph that applies , | Transformers may use this mechanism to report XML parsing errors as | well as transformation errors. ` since our test case is an XML parsing error. I'll try to modify the test to use a real transformation error instead. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
