git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: randall.s.becker@rogers.com
Cc: git@vger.kernel.org, "Randall S. Becker" <rsbecker@nexbridge.com>
Subject: Re: [Patch 0/5] Add exclusions for tests requiring cvs where cvs is not installed
Date: Thu, 13 Jun 2019 15:06:44 -0400	[thread overview]
Message-ID: <20190613190644.GC27217@sigill.intra.peff.net> (raw)
In-Reply-To: <20190613185313.16120-1-randall.s.becker@rogers.com>

On Thu, Jun 13, 2019 at 02:53:08PM -0400, randall.s.becker@rogers.com wrote:

> 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.

Hrm. I don't have cvs installed, and those tests are properly skipped
for me. That's because they include lib-cvs.sh, which has:

  if ! type cvs >/dev/null 2>&1
  then
          skip_all='skipping cvsimport tests, cvs not found'
          test_done
  fi

Why doesn't that work for you? Does the "type" check not work (e.g., you
have something called "cvs" but it does not behave as we expect)? If so,
then it sounds like we just need to harmonize that with the other
checks.

It also sounds like the t9400 tests could be using lib-cvs to avoid
duplicating logic, though it might need some refactoring (they don't
need cvsps, for example).

-Peff

  parent reply	other threads:[~2019-06-13 19:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 18:53 [Patch 0/5] Add exclusions for tests requiring cvs where cvs is not installed randall.s.becker
2019-06-13 18:53 ` [Patch 1/5] t9600-cvsimport: exclude test if " 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 ` Jeff King [this message]
2019-06-13 19:30   ` [Patch 0/5] Add exclusions for tests requiring cvs where " 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=20190613190644.GC27217@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=randall.s.becker@rogers.com \
    --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).