ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Guillory" <Stan.Guill...@wnco.com>
Subject RE: Did 1.7RC1 break JUnit 4.x compatibility?
Date Wed, 15 Nov 2006 14:56:34 GMT

We can't do snapshot views on Unix, and setting up a snapshot view on
Windows would take hours to download all the relevant portions of the
build that is failing. A reasonable simulation of a snapshot view is to
just move the code out of a view to a regular file system. I did this on
Solaris and had the same problems. 

Did 1.7 fundamentally change the way it monitors the forked Junit VM?
I'd hate to see this release candidate go final, because the only thing
I really care about in it is the ability to get meaningful test names on
my junit4 test reports. 

Stan


-----Original Message-----
From: Alexey Solofnenko [mailto:trelony@gmail.com] 
Sent: Tuesday, November 14, 2006 4:43 PM
To: Ant Developers List
Subject: Re: Did 1.7RC1 break JUnit 4.x compatibility?

In my experience dynamic views on Unix are usually much faster.  Also
permissions are important and Windows symbolic links (with \) do not
Unix.

Can you try running the tests on a snapshot view?

- Alexey.

On 11/14/06, Stan Guillory <Stan.Guillory@wnco.com> wrote:
>
> One thing is we use clearcase for source control, and we use dynamic 
> views. My original email was due to builds on unix where every test 
> failed this way. When I ran the test on Windows, in a dynamic view, 
> one test actually succeeded before the next one failed. I wonder if it

> could be a timing issue?
>
> Stan
>
>
> -----Original Message-----
> From: Stan Guillory [mailto:Stan.Guillory@wnco.com]
> Sent: Tuesday, November 14, 2006 4:18 PM
> To: Ant Developers List
> Subject: RE: Did 1.7RC1 break JUnit 4.x compatibility?
>
>
> Hmm. When I cobbled together a simple hello class with one test, and a

> real simple build file, I didn't see the problem. And the build file 
> for our project where I am seeing the problem is not simple. Let me 
> try to determine what we are doing in the large build system that 
> isn't happening in a simple standalone example.
>
> Stan
>
>
> -----Original Message-----
> From: Antoine Levy-Lambert [mailto:antoine@gmx.de]
> Sent: Tuesday, November 14, 2006 3:35 PM
> To: Ant Developers List
> Subject: Re: Did 1.7RC1 break JUnit 4.x compatibility?
>
> Hello Stan,
>
> can you create a bug report with a small build.xml file and a small 
> test class so that we can reproduce the error ?
>
> Regards,
>
> Antoine
> -------- Original-Nachricht --------
> Datum: Tue, 14 Nov 2006 14:34:03 -0600
> Von: "Stan Guillory" <Stan.Guillory@wnco.com>
> An: dev@ant.apache.org
> Betreff: Did 1.7RC1 break JUnit 4.x compatibility?
>
> > I upgraded from 1.6.5 to 1.7RC1 today and immediately hit the "Can't

> > find junitvmwatcher.90872" issue that was present in the early
betas.
> >
> > Thanks,
> > Stan
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional 
> commands, e-mail: dev-help@ant.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional 
> commands, e-mail: dev-help@ant.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional 
> commands, e-mail: dev-help@ant.apache.org
>
>


--
Alexey N. Solofnenko trelony at gmail.com
home: http://trelony.cjb.net/
Pleasant Hill, CA (GMT-8 hours usually)

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


Mime
View raw message