To take a different approach: have you considered using a continuous
integration server? This is exactly the sort of thing they're good at, and
then your ant setup could just worry about building.
I've used TeamCity and have heard good things about Jenkins (
http://jenkins-ci.org/), but probably
s the log was not kept,
> which is important for error situations. But they are easy to set up,
> so it worth investigating.
>
> --glenn
>
>
>
> On Fri, Aug 5, 2011 at 09:32, Laura Dean
> wrote:
> > To take a different approach: have you considered using a continuou
As I read it, that's the expected behavior:
When running multiple tests inside the same Java VM (see forkMode),
timeout applies to the time that all tests use together, not to an
individual test.
http://ant.apache.org/manual/Tasks/junit.html
You have forkMode set to once, which means
My team has a unit test suite that ran in about a minute and a half
with ant 1.6.5 (and 1.7.1), but now takes over 4 minutes with ant
1.8.1 (or 1.8.0). Has anyone else had this problem? The closest I've
found via google is here, but it doesn't shed much light on the
subject:
http://netbeans.org/
On Wed, Jul 21, 2010 at 7:26 PM, Martin Gainty wrote:
>
> what processor have you implemented in your testbed platform?
On this particular machine, windows reports:
Intel(R) Core(TM) i7 CPU 940 @ 2.93 GHz
> how much ram on your testbed platform?
6 GB
We've seen the same behavior on our less
The "echo" task should let you do either of those.
Laura
On Thu, Jul 22, 2010 at 12:13 PM, Ben Stover wrote:
> Is there a way to output/write the current value (during runtime) of an ANT
> variable onto a console or into a text file?
>
> How does that work in detail?
>
> Ben
--
ay, but I will look at
it then.
Laura
On Fri, Jul 23, 2010 at 1:10 AM, Stefan Bodewig wrote:
> On 2010-07-22, Laura Dean wrote:
>
> > My team has a unit test suite that ran in about a minute and a half
> > with ant 1.6.5 (and 1.7.1), but now takes over 4 minutes with ant
>
Bodewig wrote:
>>
>> On 2010-07-22, Laura Dean wrote:
>>
>> > My team has a unit test suite that ran in about a minute and a half
>> > with ant 1.6.5 (and 1.7.1), but now takes over 4 minutes with ant
>> > 1.8.1 (or 1.8.0). Has anyone else had this problem?
1.8.
* Like you, I also couldn't reproduce the problem under linux.
Laura
>> On Fri, Jul 23, 2010 at 1:10 AM, Stefan Bodewig wrote:
>>>
>>> On 2010-07-22, Laura Dean wrote:
>>>
>>> > My team has a unit test suite that ran in about a minute an
On Wed, Jul 28, 2010 at 6:44 AM, Stefan Bodewig wrote:
>
...
> OK, I'll look into this when I get access to my Windows machine again
> next week. It didn't take more than the small test case you provided to
> see the difference, right?
Right. The small test case was enough to see the difference
On Thu, Aug 19, 2010 at 8:54 AM, Stefan Bodewig wrote:
> The change has been implemented in svn trunk[1] and may become part of
> the next Ant release. Using svn trunk my tests run as fast (or even
> faster) as they do using Ant 1.7.1.
Thank you very much! We'll definitely try it out.
> To be
this fork at all;
we just put it there for our convenience, and I mention it now it in
case it saves anyone else a little work.
Thanks again!
Laura
On Thu, Aug 19, 2010 at 11:10 AM, Laura Dean wrote:
> On Thu, Aug 19, 2010 at 8:54 AM, Stefan Bodewig wrote:
>> The change has been imple
12 matches
Mail list logo
