From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [StGit PATCH] Remove broken branch creation subtest
Date: Sat, 12 Apr 2008 14:44:15 +0200 [thread overview]
Message-ID: <20080412124212.27748.21332.stgit@yoghurt> (raw)
This subtest has started to cause subsequent subtests to fail with
recent versions of git. And I don't think we can blame this one on
git. What the subtest does is:
1. Remove all files or directories called "foo" under .git/. This is
supposed to delete the "foo" branch and associated StGit files,
but what about packed refs? This isn't actually malfunctioning
yet as far as I can tell, but it's a ticking bomb.
2. Create an empty file .git/refs/heads/foo. This is supposed to be
a "broken branch", and indeed it is -- for example, git show-ref
barfs on such a repository even if asked to only show a branch
other than foo!
3. Makes sure that stg branch won't successfully create a "foo"
branch. I'm pretty sure this fails because git thinks the repo is
broken, not because stg handles it gracefully. This is what the
test is supposed to be testing, but if we wanted that, we'd need
a more detailed test.
4. Doesn't clean up the broken ref, which causes some subsequent
subtests to fail.
What probably happened is that git got ever so slightly fussier about
broken refs, so that (4) became a problem.
Signed-off-by: Karl Hasselström <kha@treskal.com>
---
This should go to the stable branch. (master is affected too, but a
merge will fix that.)
t/t1000-branch-create.sh | 7 -------
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/t/t1000-branch-create.sh b/t/t1000-branch-create.sh
index d6cf34a..298eb1a 100755
--- a/t/t1000-branch-create.sh
+++ b/t/t1000-branch-create.sh
@@ -54,13 +54,6 @@ test_expect_success \
'
test_expect_success \
- 'Create an invalid refs/heads/ entry' '
- find .git -name foo | xargs rm -rf &&
- touch .git/refs/heads/foo &&
- ! stg branch -c foo
-'
-
-test_expect_success \
'Setup two commits including removal of generated files' '
git init &&
touch a.c a.o &&
next reply other threads:[~2008-04-12 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 12:44 Karl Hasselström [this message]
2008-04-12 18:06 ` [StGit PATCH] Remove broken branch creation subtest Junio C Hamano
2008-04-13 6:02 ` Karl Hasselström
2008-04-13 13:43 ` [StGit PATCH] Fix problems in t1000-branch-create Karl Hasselström
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=20080412124212.27748.21332.stgit@yoghurt \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
/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).