From: A Large Angry SCM <gitzilla@gmail.com>
To: git@vger.kernel.org
Subject: t9118 broken in current master, 9918285, git/git/v1.7.2-rc2
Date: Wed, 07 Jul 2010 21:49:41 -0400 [thread overview]
Message-ID: <4C352EB5.5020005@gmail.com> (raw)
I've been busy with other projects and haven't attempted a full make &
make test since f526d12, which did pass all the tests. Since the test
name implies svn/git-svn breakage, I hoping the git-svn experts can find
the problem.
This was on an amd64 Debian Squeeze system, up to date as of about 13:00
EDT today.
*** t9118-git-svn-funky-branch-names.sh ***
ok 1 - setup svnrepo
not ok - 2 test clone with funky branch names
#
# git svn clone -s "$svnrepo/pr ject" project &&
# cd project &&
# git rev-parse "refs/remotes/fun%20plugin" &&
# git rev-parse "refs/remotes/more%20fun%20plugin!" &&
# git rev-parse "refs/remotes/$scary_ref" &&
# git rev-parse "refs/remotes/%2Eleading_dot" &&
# git rev-parse "refs/remotes/trailing_dot%2E" &&
# git rev-parse
"refs/remotes/trailing_dotlock%2Elock" &&
# git rev-parse "refs/remotes/not-a%40{0}reflog" &&
# cd ..
#
not ok - 3 test dcommit to funky branch
#
# cd project &&
# git reset --hard 'refs/remotes/more%20fun%20plugin!' &&
# echo hello >> foo &&
# git commit -m 'hello' -- foo &&
# git svn dcommit &&
# cd ..
#
not ok - 4 test dcommit to scary branch
#
# cd project &&
# git reset --hard "refs/remotes/$scary_ref" &&
# echo urls are scary >> foo &&
# git commit -m "eep" -- foo &&
# git svn dcommit &&
# cd ..
#
not ok - 5 test dcommit to trailing_dotlock branch
#
# cd project &&
# git reset --hard "refs/remotes/trailing_dotlock%2Elock" &&
# echo who names branches like this anyway? >> foo &&
# git commit -m "bar" -- foo &&
# git svn dcommit &&
# cd ..
#
# failed 4 among 5 test(s)
next reply other threads:[~2010-07-08 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 1:49 A Large Angry SCM [this message]
2010-07-08 3:15 ` t9118 broken in current master, 9918285, git/git/v1.7.2-rc2 Brian Gernhardt
2010-07-08 3:42 ` Brian Gernhardt
2010-07-08 14:06 ` A Large Angry SCM
2010-07-08 13:36 ` [PATCH] t9118 (git-svn): prevent early failure from taking down later tests Jonathan Nieder
2010-07-08 14:35 ` A Large Angry SCM
2010-07-08 16:48 ` Jonathan Nieder
2010-07-08 20:59 ` Eric Wong
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=4C352EB5.5020005@gmail.com \
--to=gitzilla@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.