ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francis GALIEGUE <...@one2team.com>
Subject Re: Help with bug diagnosis: <junitreport> task takes 30+ minutes to complete
Date Tue, 15 Sep 2009 06:40:43 GMT
On Mon, Sep 14, 2009 at 13:25, Steve Loughran <stevel@apache.org> wrote:
> Francis GALIEGUE wrote:
> ort 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?
>>
>
>
> That'll be the stdout taking up most of the space. Try cranking back the
> Log4J settings of whatever is printing so much out.
>

I've found out the culprit... The dev team has a custom file
comparison assertion that prints out the whole content of the files
into the report itself. Meh.

> I've played with junit outputs that chuck out XHTML direct, rather than an
> XML that needs transforming. You still have that option, but it isn't
> compulsory.
>

That looks interesting, since we don't need the XML output anymore (it
was needed before for some obscure, false reason). I don't see that
option in ant's manual. Is this a future enhancement?

-- 

Francis Galiegue
ONE2TEAM
Ingénieur système
Mob : +33 (0) 683 877 875
Tel : +33 (0) 178 945 552
fge@one2team.com
40 avenue Raymond Poincaré
75116 Paris

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message