git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: t9010 broken in pu [Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)]
Date: Wed, 8 Dec 2010 05:28:36 -0600	[thread overview]
Message-ID: <20101208112836.GA5285@burratino> (raw)
In-Reply-To: <201012081223.47642.trast@student.ethz.ch>

Thomas Rast wrote:

> If I'm reading the test report right, the merge conflict in
> t/t9010-svn-fe.sh broke tests.  It bisects to 5ea8b68 (Merge branch
> 'jn/svn-fe' into pu, 2010-12-07), failing with
[...]
> A quick reading of the merge suggests that you concatenated with an
> earlier test that goes
> 
>   test_dump () {
[...]
> hence creating simple-svn, too.  So a rename or rm -rf should suffice.

Thanks for the analysis.  Even better would be to remove the redundant
definition and invocation of test_dump, like this (imitating b3e5bce,
vcs-svn: Error out for v3 dumps, 2010-11-17):
---
diff --git a/t/t9010-svn-fe.sh b/t/t9010-svn-fe.sh
index 6e3b6ad..d207aeb 100755
--- a/t/t9010-svn-fe.sh
+++ b/t/t9010-svn-fe.sh
@@ -14,31 +14,6 @@ svn_cmd () {
 	svn "$subcommand" --config-dir "$svnconf" "$@"
 }
 
-test_dump () {
-	label=$1
-	dump=$2
-	test_expect_success "$dump" '
-		svnadmin create "$label-svn" &&
-		svnadmin load "$label-svn" < "$TEST_DIRECTORY/$dump" &&
-		svn_cmd export "file://$PWD/$label-svn" "$label-svnco" &&
-		git init "$label-git" &&
-		test-svn-fe "$TEST_DIRECTORY/$dump" >"$label.fe" &&
-		(
-			cd "$label-git" &&
-			git fast-import < ../"$label.fe"
-		) &&
-		(
-			cd "$label-svnco" &&
-			git init &&
-			git add . &&
-			git fetch "../$label-git" master &&
-			git diff --exit-code FETCH_HEAD
-		)
-	'
-}
-
-test_dump simple t9135/svn.dump
-
 reinit_git () {
 	rm -fr .git &&
 	git init

      reply	other threads:[~2010-12-08 11:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05  6:30 What's cooking in git.git (Dec 2010, #01; Sat, 4) Junio C Hamano
2010-12-05  7:39 ` Jeff King
2010-12-05 19:54   ` Junio C Hamano
2010-12-06  0:54     ` aleksi.aalto
2010-12-09 17:27     ` Jeff King
2010-12-10 19:55       ` Junio C Hamano
2010-12-05 10:13 ` Yann Dirson
2010-12-05 20:23   ` Junio C Hamano
2010-12-06  7:29     ` Yann Dirson
2010-12-06  8:13       ` Miles Bader
2010-12-06  8:21         ` Yann Dirson
2010-12-06  8:39           ` Miles Bader
2010-12-06  8:48             ` Yann Dirson
2010-12-06  9:13               ` Miles Bader
2010-12-06 11:31                 ` Yann Dirson
2010-12-06 11:37                 ` Matthieu Moy
2010-12-10 21:59                 ` Junio C Hamano
2010-12-05 12:36 ` aleksi.aalto
2010-12-05 15:51   ` Patrick Rouleau
2010-12-05 13:00 ` Erik Faye-Lund
2010-12-05 20:15   ` Junio C Hamano
2010-12-05 15:00 ` Michael J Gruber
2010-12-05 20:06   ` Junio C Hamano
2010-12-06  8:55     ` Michael J Gruber
2010-12-06 15:39       ` Thiago Farina
2010-12-08 11:23 ` t9010 broken in pu [Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)] Thomas Rast
2010-12-08 11:28   ` Jonathan Nieder [this message]

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=20101208112836.GA5285@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=trast@student.ethz.ch \
    /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).