From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: A Large Angry SCM <gitzilla@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH] t9010: svnadmin can fail even if available
Date: Thu, 6 Jan 2011 14:46:05 -0600 [thread overview]
Message-ID: <20110106204605.GA15090@burratino> (raw)
In-Reply-To: <7vpqs9aiul.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> But I am somewhat unhappy because I do not think we want to cater to all
> the broken installations of system tools. When tests fail because
> somebody's "mkdir -p" (just a random example I picked from your patch)
> does not work correctly, we would just say "Your system is broken, and
> here is a nickle; get a better computer". Why is svnadmin so special?
>
> Also isn't the breakage not just this test, but also in all the tests that
> try to run "svnadmin load"? Shouldn't we somehow hoist this logic out of
> t9010 and put it in t/lib-vcs-svn.sh or somewhere?
>
> As far as I understand, svn interoperability bits (git-svn and vcs-svn) do
> not rely on svnadmin at runtime, so a breakage in the system's svnadmin
> would not be a reason to omit building and installing them.
You're right, I did not do a good job of selling the patch. I should
have said:
Subject: t9010: svnadmin can fail even if available
If svn is built against one version of SQLite and run against
another, libsvn_subr needlessly errors out in operations that
need to make a commit.
That is clearly not a bug in git but let us consider the
ramifications for the test suite. git-svn uses libsvn directly
and is probably broken by that bug; it is right for git-svn
tests to fail. The vcs-svn lib, on the other hand, does not use
libsvn and the test t9010 only uses svn to check its work. This
points to two possible improvements:
- do not disable most vcs-svn tests if svn is missing.
- skip validation rather than failing it when svn fails.
Bring about both by putting the svn invocations into a single
test that builds a repo to compare the test-svn-fe result
against. The test will always pass but only will set the new
SVNREPO test prereq if svn succeeds; and validation using that
repo gets an SVNREPO prerequisite so it only runs with working
svn installations.
Works-around: http://bugs.debian.org/608925
Noticed-by: A Large Angry SCM <gitzilla@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
next prev parent reply other threads:[~2011-01-06 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 16:04 Repeatable test t9010-svn-fe.sh failure w/ master (685e9d9, 1.7.4.rc1) A Large Angry SCM
2011-01-06 16:59 ` Jonathan Nieder
2011-01-06 17:20 ` A Large Angry SCM
2011-01-06 18:00 ` [PATCH] t9010: svnadmin can fail even if available Jonathan Nieder
2011-01-06 18:32 ` A Large Angry SCM
2011-01-06 20:16 ` Junio C Hamano
2011-01-06 20:46 ` Jonathan Nieder [this message]
2011-01-07 1:07 ` Junio C Hamano
2011-01-07 1:31 ` Jonathan Nieder
2011-01-07 16:58 ` Ramkumar Ramachandra
2011-01-07 18:54 ` Junio C Hamano
2011-01-06 18:15 ` Repeatable test t9010-svn-fe.sh failure w/ master (685e9d9, 1.7.4.rc1) Junio C Hamano
2011-01-06 19:06 ` A Large Angry SCM
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110106204605.GA15090@burratino \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).