[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 3311 - trunk/subversion/include trunk/subversion/libsvn_wc trunk/subversion/libsvn_subr trunk/subversion/libsvn_client trunk/subversion/tests/clients/cmdline trunk/subversion/tests

From: Brian Denny <brian_at_briandenny.net>
Date: 2002-10-08 19:50:44 CEST

On 8 Oct 2002 cmpilato@collab.net wrote:

> The tests itself is posix-only? As in it only runs on posix
> platforms? I don't recall your original test doing that, and don't
> see the need for the new test to do so either. Further, I'm worried
> about any situation that might result in a test seeming to exist on
> one platform and not another (you know, it's nice to say "basic-test
> 9" instead of "basic-test 9, or basic-test 8 on windows"). :-)

the test is there, but just returns success on non-posix platforms,
so it doesn't throw off the numbering.

see schedule_tests.py: *_executable.

> It seems the 'posix-only' portions of the test are small enough
> to just be conditional pieces of a generic test that should run
> everywhere.

that's definitely doable.

i could also change the *_executable tests in schedule_tests.py so that
they still do something on windows. but of course, these really wouldn't
be testing anything that other tests don't cover, and 'add_executable'
would be a misnomer. i suppose i could fold the executable test into
the previously-existing schedule.py tests...

-brian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 8 19:56:24 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.