On Tue, Sep 1, 2009 at 15:31, Francis GALIEGUE<f...@one2team.com> wrote: [...] > > I have the following setup: > > * running on CentOS 5, 64 bits; > * using ant 1.6.5, packaged by JPackage; > * using Sun's latest Java 6 (JVM + JDK), 32bit (yes, even though I run > a 64bit OS, but I need the 32bit JDK since I use a 32bit oracle > driver, I've no choice); > * I have the following in my classpath: > /usr/share/java/saxon.jar:/usr/share/java/ant-contrib.jar:/usr/share/java/xalan-j2-serializer.jar > (saxon 6.3.5, ant-contrib 1.0b2, xalan-j2 2.0.7) > > I have the means to restrict the test suite. For some test suites (I > don't have an exact, restricted test suite that triggers the problem), > the <junitreport> task takes more than 30 minutes to generate the > reports. The snippet from the ant file is as such: > > ---- > <junitreport tofile="${junit.summaryfile}"> > <fileset dir="${junit.reports}" includes="TEST-*.xml"/> > <report format="frames" todir="${junit.htmlreport}"/> > <report format="noframes" todir="${junit.htmlreport}"/> > </junitreport> > ---- > > I surmise that the <report format="frames"/> is the culprit here, > since both <report> tasks output the generation time. The noframes > report is fairly quick. > > How can I diagnose the problem precisely? Can I use another XSL > processor that will be faster than xalan-j2? >
Well, a simple ant -v showed the problem, as it shows which files are parsed. The two bigger files are 10 MB and 9 MB respectively! The sheer size of them is huge, but does it explain the 10+ minutes parsing time? -- Francis Galiegue ONE2TEAM Ingénieur système Mob : +33 (0) 683 877 875 Tel : +33 (0) 178 945 552 f...@one2team.com 40 avenue Raymond Poincaré 75116 Paris --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org