From: randall.s.becker@rogers.com
To: git@vger.kernel.org
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>
Subject: [Patch 0/5] Add exclusions for tests requiring cvs where cvs is not installed
Date: Thu, 13 Jun 2019 14:53:08 -0400 [thread overview]
Message-ID: <20190613185313.16120-1-randall.s.becker@rogers.com> (raw)
From: "Randall S. Becker" <rsbecker@nexbridge.com>
t9600 to t9604 currently depend on cvs to function correctly, otherwise
all of those tests fail. This patch follows an existing pattern of
from the t9400 series by attempting to run cvs without arguments,
which succeeds if installed, and skipping the test if the command
fails.
Randall S. Becker (5):
t9600-cvsimport: exclude test if cvs is not installed
t9601-cvsimport-vendor-branch: exclude test if cvs is not installed
t9602-cvsimport-branches-tags: exclude test if cvs is not installed
t9603-cvsimport-patchsets: exclude test if cvs is not installed
t9604-cvsimport-timestamps: exclude test if cvs is not installed
t/t9600-cvsimport.sh | 7 +++++++
t/t9601-cvsimport-vendor-branch.sh | 8 ++++++++
t/t9602-cvsimport-branches-tags.sh | 7 +++++++
t/t9603-cvsimport-patchsets.sh | 7 +++++++
t/t9604-cvsimport-timestamps.sh | 7 +++++++
5 files changed, 36 insertions(+)
--
2.22.0
next reply other threads:[~2019-06-13 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 18:53 randall.s.becker [this message]
2019-06-13 18:53 ` [Patch 1/5] t9600-cvsimport: exclude test if cvs is not installed randall.s.becker
2019-06-13 18:53 ` [Patch 2/5] t9601-cvsimport-vendor-branch: " randall.s.becker
2019-06-13 18:53 ` [Patch 3/5] t9602-cvsimport-branches-tags: " randall.s.becker
2019-06-13 18:53 ` [Patch 4/5] t9603-cvsimport-patchsets: " randall.s.becker
2019-06-13 18:53 ` [Patch 5/5] t9604-cvsimport-timestamps: " randall.s.becker
2019-06-13 19:06 ` [Patch 0/5] Add exclusions for tests requiring cvs where " Jeff King
2019-06-13 19:30 ` Randall S. Becker
2019-06-13 22:46 ` Randall S. Becker
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190613185313.16120-1-randall.s.becker@rogers.com \
--to=randall.s.becker@rogers.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).