From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: Lars Hjemli <hjemli@gmail.com>
Subject: [PATCH 0/3] t7400-submodule-basic.sh cleanups
Date: Sat, 10 Apr 2010 00:37:29 -0500 [thread overview]
Message-ID: <20100410053729.GA17595@progeny.tock> (raw)
The 'update --init' test from t7400 is failing on a few machines
I don’t have access to. It’s hard to say what the dangerous
ingredient is --- maybe a libc bug or something. [1]
I took the opportunity to clarify what some of the tests do and to
make the output a little more helpful.
This series has three patches for easier review, but it might make
sense to squash them; alternatively, it might make sense to split the
test into several files.
What do you think?
Jonathan Nieder (3):
t7400: split setup into multiple tests
t7400: clarify 'submodule add' tests
t7400: clarify submodule update tests
t/t7400-submodule-basic.sh | 331 +++++++++++++++++++++++++++-----------------
1 files changed, 201 insertions(+), 130 deletions(-)
[1] You can see some logged test failures at [2] [3], though it isn’t
very illuminating. Well, that’s more of something for a Debian
Developer or someone with access to a similar machine to investigate.
[2] <https://buildd.debian.org/build.cgi?pkg=git-core>
[3] <http://bugs.debian.org/569594>.
next reply other threads:[~2010-04-10 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 5:37 Jonathan Nieder [this message]
2010-04-10 5:38 ` [PATCH 1/3] t7400: split setup into multiple tests Jonathan Nieder
2010-04-10 5:39 ` [PATCH 2/3] t7400: clarify 'submodule add' tests Jonathan Nieder
2010-04-10 5:39 ` [PATCH 3/3] t7400: clarify submodule update tests Jonathan Nieder
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=20100410053729.GA17595@progeny.tock \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hjemli@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).