git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: 'git mailing list' <git@vger.kernel.org>
Subject: Re: Request for Assist on Limits for Tests
Date: Sun, 7 Jan 2018 21:18:29 +0000	[thread overview]
Message-ID: <20180107211829.GA5946@genre.crustytoothpaste.net> (raw)
In-Reply-To: <000d01d387fa$36a65300$a3f2f900$@nexbridge.com>

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

On Sun, Jan 07, 2018 at 03:57:59PM -0500, Randall S. Becker wrote:
> I'm looking for a proper (i.e. not sneaky) way to detect the platform I am
> on during testing so that some tests can be modified/skipped other than
> using the standard set of dependencies. In particular, the maximum path on
> current NonStop platforms is 8-bit 2048 bytes. It appears that there are
> some tests - at least from my preliminary "guessing" - that are beyond that
> limit once all of the path segments are put together. I would rather have
> something in git that specifies a path size limit so nothing exceeds it, but
> that may be wishing.

The way we usually skip tests automatically is with a test prerequisite.
You might look at t/test-lib.sh for the test_set_prereq and
test_lazy_prereq calls and synthesize one (maybe LONG_PATHS) that meets
your needs.  You can then annotate those tests with the appropriate
prerequisite.

I expect that for long paths, you will hit a lot of the same issues as
occur on Windows, where PATH_MAX may be very small.  It might be
valuable to expose this information as a build option and then set an
appropriate variable in t/test-lib.sh.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]

  reply	other threads:[~2018-01-07 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 20:57 Request for Assist on Limits for Tests Randall S. Becker
2018-01-07 21:18 ` brian m. carlson [this message]
2018-01-08 17:44   ` 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=20180107211829.GA5946@genre.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --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).