--On Friday, January 7, 2005 4:21 AM -1000 [EMAIL PROTECTED] wrote:

Hackystat build (configuration Hackystat-ALL) failed.
Build report is available at
http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?year
=2005&month=1&day=7&configuration=Hackystat-ALL Build Time Stamp: Fri Jan
07 04:21:53 HST 2005

OK, well the first thing to make clear is that all three build failures are due to me and DocBook. Ironically, and rather humorously, the hackystat-UH configuration (the one that I actually tested out yesterday) is the only one of the four that passes!


- The JPL and Cocomo configurations failed because my docbook build script failed to account for a boundary condition (i.e. when there are no sensors defined in a configuration). That should be easy to reproduce and fix.

- The ALL configuration fails with the following error:

Caused by: javax.xml.transform.TransformerFactoryConfigurationError: Provider com.icl.saxon.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:
100)
at org.hackystat.perf.report.Xml2HtmlReportTransformer.transform(Xml2HtmlRepor
tTransformer.java:133)
at org.hackystat.perf.HackyPerfAntReportTask.execute(HackyPerfAntReportTask.ja
va:80)


This is a little more unsettling: it's another manifestation of the fact that my DocBook/Ant system requires an idiosyncratic set of XML processing libraries that are not compatible with the rest of our build system. My guess (since the UH config did pass last night) is that moving docbook after junit was good enough to get UH to pass, but ALL fails because it also runs hackyPerf and DocBook currently precedes hackyPerf in the build.

I will fiddle with this today. Hopefully I can move the DocBook target around in the cruisecontrol target to a point where it's invoked last, after all other targets that need different versions of the XML libraries.

Of course, a better solution would be to figure out if there's a configuration of XML libraries that works for DocBook and Hackystat simultaneously. That's a task for another day, though.

Cheers,
Philip










Reply via email to