Re: Gump issue fixed

Mon, 28 Feb 2011 00:04:24 -0800 

test-ooxml now passes, but we need one more fix to make Gump quiet.
Today's warning was caused by the missing excelant dependency in Gump's poi.xml. I committed this fix in r1075179, see https://svn.apache.org/repos/asf/gump/metadata/project/poi.xml.
I'm waiting for two successful Gump cycles and then will build a release candidate 3.8-beta1. 

Yegor

On 2/26/2011 11:55 PM, Yegor Kozlov wrote:
Getting daily Gump warnings was quite annoying. We are going to release a beta and with failed Gump it wouldn't be wise.
I hope I fixed it. Something has changed in the Xerces' schema validation engine and it started to reject nodes with Node.getLocalName() returning null. I don't know if it is a bug or intentional an change. 

How to replicate:

 1. checkout Xerces trunk and build xercesImpl.jar
2. fork POI's build.xml and change the ooxml-test-runner macro as follows: 

<!-- all xml dependencies except xercesImpl.jar -->
<property name="tools.dir" value="/java/apache/apache-xerces/trunk/tools"/> 
<!-- the directory with xercesImpl.jar -->
<property name="build.dir" value="/java/apache/apache-xerces/trunk/build"/> 

<property name='jar.apis' value='xml-apis.jar'/>
<property name='jar.resolver' value='resolver.jar'/>
<property name='jar.serializer' value='serializer.jar'/>
<property name='jar.xalan' value='xalan.jar'/>
<property name='jar.xerces' value='xercesImpl.jar'/>

<macrodef name="ooxml-test-runner">
<attribute name="classpath"/>
<sequential>
<junit printsummary="yes" fork="yes" forkmode="once" haltonfailure="${halt.on.test.failure}" 
                 failureproperty="ooxml.test.failed">
<classpath refid="@{classpath}"/>
<syspropertyset refid="junit.properties"/>
<jvmarg value="${poi.test.locale}"/>
<jvmarg value="-Xbootclasspath/p:${tools.dir}/${jar.apis}${path.separator}${tools.dir}/${jar.resolver}${path.separator}${tools.dir}/${jar.serializer}${path.separator}${build.dir}/${jar.xerces}${path.separator}${tools.dir}/${jar.xalan}"/> 

<formatter type="plain"/>
<batchtest todir="${ooxml.reports.test}">
<fileset dir="${ooxml.src.test}">
<include name="**/TestXSSFExportToXML.java"/>
</fileset>
</batchtest>
</junit>
</sequential>
</macrodef>
Note the trick with the -Xbootclasspath argument. JDK includes a version of Xerces and to override it you need to pass a custom boot classpath. 

 3. Running "ant test-ooxml" should fail with the same exception as Gump

The fix is easy, but it took me two days to figure out the problem :).
Nodes created using Document.createElement(nodeName) are bad and not validated, but Document.createElementNS("", nodeName) works. The same things with attributes: Document.createAttribute(nodeName) fails, but Document.createAttributeNS("", nodeName) works. 

Fixed in r1074920

Yegor

On 2/26/2011 8:21 AM, Gump [HEAD] :-( 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 [email protected].

Project poi-test has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'. 
For reference only, the following projects are affected by this:
     - poi-test :  POI


Full details are available at:
     http://vmgump.apache.org/gump/public/poi/poi-test/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
-INFO- Project Reports in: /srv/gump/public/workspace/poi/build/test-results -INFO- Project Reports in: /srv/gump/public/workspace/poi/build/scratchpad-test-results -INFO- Project Reports in: /srv/gump/public/workspace/poi/build/ooxml-test-results 



The following work was performed:
http://vmgump.apache.org/gump/public/poi/poi-test/gump_work/build_poi_poi-test.html 
Work Name: build_poi_poi-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 21 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only -Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dversion.id=gump -DDSTAMP=26022011 test 
[Working Directory: /srv/gump/public/workspace/poi]
CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/poi/build/test-classes:/srv/gump/public/workspace/poi/build/scratchpad-test-classes:/srv/gump/public/workspace/poi/build/ooxml-test-classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.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/logging-log4j-12/dist/lib/log4j-26022011.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-26022011.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-26022011.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-26022011.jar:/srv/gump/public/workspace/commons-collecti ons-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/commons-lang-2.x/target/commons-lang-2.7-SNAPSHOT.jar:/srv/gump/public/workspace/junit/dist/junit-26022011.jar:/srv/gump/public/workspace/junit/dist/junit-dep-26022011.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/poi/build/dist/poi-gump-26022011.jar:/srv/gump/public/workspace/poi/build/dist/poi-scratchpad-gump-26022011.jar:/srv/gump/public/workspace/poi/build/dist/poi-ooxml-gump-26022011.jar:/srv/gump/public/workspace/poi/ooxml-lib/stax-api-1.0.1.jar:/srv/gump/public/workspace/poi/ooxml-lib/xmlbeans-2.3.0.jar:/srv/gump/public/workspace/poi/ooxml-lib/ooxml-schemas-1.1.jar 
---------------------------------------------
     [junit] Running org.apache.poi.openxml4j.opc.TestFileHelper
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.002 sec 
     [junit] Running org.apache.poi.openxml4j.opc.TestListParts
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.029 sec 
     [junit] Running org.apache.poi.openxml4j.opc.TestPackage
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 0.499 sec [junit] Running org.apache.poi.openxml4j.opc.TestPackageCoreProperties [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.048 sec 
     [junit] Running org.apache.poi.openxml4j.opc.TestPackagePartName
     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec
     [junit] Running org.apache.poi.openxml4j.opc.TestPackageThumbnail
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.042 sec 
     [junit] Running org.apache.poi.openxml4j.opc.TestPackagingURIHelper
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.016 sec 
     [junit] Running org.apache.poi.openxml4j.opc.TestRelationships
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.19 sec [junit] Running org.apache.poi.openxml4j.opc.compliance.TestOPCComplianceCoreProperties [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.086 sec [junit] Running org.apache.poi.openxml4j.opc.compliance.TestOPCCompliancePackageModel [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.017 sec [junit] Running org.apache.poi.openxml4j.opc.compliance.TestOPCCompliancePartName [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.021 sec [junit] Running org.apache.poi.openxml4j.opc.internal.TestContentTypeManager [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.005 sec 
     [junit] Running org.apache.poi.ss.TestWorkbookFactory
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.104 sec 
     [junit] Running org.apache.poi.ss.format.TestCellFormatPart
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 3.433 sec 
     [junit] Running org.apache.poi.xslf.TestXSLFSlideShow
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.397 sec [junit] Running org.apache.poi.xslf.extractor.TestXSLFPowerPointExtractor [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.034 sec 
     [junit] Running org.apache.poi.xssf.TestSheetProtection
[junit] Tests run: 17, Failures: 0, Errors: 0, Time elapsed: 0.392 sec 
     [junit] Running org.apache.poi.xssf.TestWorkbookProtection
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.187 sec 
     [junit] Running org.apache.poi.xssf.eventusermodel.TestXSSFReader
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.234 sec [junit] Running org.apache.poi.xssf.extractor.TestXSSFEventBasedExcelExtractor [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.94 sec [junit] Running org.apache.poi.xssf.extractor.TestXSSFExcelExtractor [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 2.259 sec 
     [junit] Running org.apache.poi.xssf.extractor.TestXSSFExportToXML
[junit] Tests run: 4, Failures: 0, Errors: 3, Time elapsed: 0.725 sec 

BUILD FAILED
/srv/gump/public/workspace/poi/build.xml:694: The following error occurred while executing this line: 
/srv/gump/public/workspace/poi/build.xml:678: Tests failed

Total time: 1 minute 21 seconds
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/poi/poi-test/rss.xml
- Atom: http://vmgump.apache.org/gump/public/poi/poi-test/atom.xml

============================== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 06000626022011, vmgump.apache.org:vmgump:06000626022011
Gump E-mail Identifier (unique within run) #11.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]








---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to