Re: Request for Assist on Limits for Tests
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Jan 7, 2018, 21:18 UTC
- Message-ID
- <20180107211829.GA5946@genre.crustytoothpaste.net>
- In-Reply-To
- <000d01d387fa$36a65300$a3f2f900$@nexbridge.com>
On Sun, Jan 07, 2018 at 03:57:59PM -0500, Randall S. Becker wrote:
Show 8 quoted lines
> 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