You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Kevin Jackson <fo...@gmail.com> on 2007/05/12 07:38:12 UTC
Antunit timings inaccurate?
Hi all,
Just writing some antunit tests for a new condition and got this in the output:
[antunit] took 1,178,948,204.551 sec
That's a long time!
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
RE: Antunit timings inaccurate?
Posted by Stephen McConnell <mc...@dpml.net>.
> -----Original Message-----
> From: Kevin Jackson [mailto:foamdino@gmail.com]
> Sent: Saturday, 12 May 2007 3:08 PM
> To: Ant Developers List
> Subject: Antunit timings inaccurate?
>
> Hi all,
>
> Just writing some antunit tests for a new condition and got
> this in the output:
>
> [antunit] took 1,178,948,204.551 sec
>
> That's a long time!
Just a touch over 37 years.
/Steve.
--------------------------
Stephen McConnell
mailto:mcconnell@dpml.net
http://www.dpml.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Antunit timings inaccurate?
Posted by Kevin Jackson <fo...@gmail.com>.
> Steve had a similar case once, I vaguely recall it was related to
> forking during the tests, but may be wrong.
>
> What have your tests been doing?
The test was the one for <resourcecontains> (which may be refactored
to a macro based on Matt's feedback)
So it was simply comparing if a resource contained a substring - I
don't think any forking was involved
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Antunit timings inaccurate?
Posted by Stefan Bodewig <bo...@apache.org>.
On Sat, 12 May 2007, Kevin Jackson <fo...@gmail.com> wrote:
> Just writing some antunit tests for a new condition and got this in
> the output:
>
> [antunit] took 1,178,948,204.551 sec
>
> That's a long time!
so to answer the question in your subject: yes, the timing is not
quite exact, it may be off by a few decenia.
Steve had a similar case once, I vaguely recall it was related to
forking during the tests, but may be wrong.
What have your tests been doing?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org