mirror of
https://git.openafs.org/openafs.git
synced 2025-01-18 15:00:12 +00:00
4db3775c0f
Currently our perl tests use Test::More, which sends diag() messages to stderr, including when reporting why a test failed. Our 'runtests' harness from c-tap-harness discards stderr from test programs, unless we run in single-test mode (-o). As a result, when we run tests with 'runtests -v' and a test fails, we can't see any diagnostic information if the test was using perl's Test::More, including why a test failed. If the test is written in C using c-tap-harness bindings, diag() goes to stdout, and this problem doesn't happen. To make sure we can see diag() messages from perl tests, change the default behavior for Test::More to print diag() messages to stdout, where they will be read by 'runtests' and shown by 'runtests -v'. The diag messages are still discarded when running in non-v (and non-o) mode. Change-Id: I971a61cb9c83e85949ba6adf9af0ee54b0b23680 Reviewed-on: https://gerrit.openafs.org/15734 Tested-by: Andrew Deason <adeason@sinenomine.net> Reviewed-by: Michael Meffie <mmeffie@sinenomine.net> |
||
---|---|---|
build-tools | ||
doc | ||
src | ||
tests | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.splintrc | ||
acinclude.m4 | ||
CODING | ||
configure-libafs.ac | ||
configure.ac | ||
CONTRIBUTING | ||
INSTALL | ||
libafsdep | ||
LICENSE | ||
Makefile-libafs.in | ||
Makefile.in | ||
NEWS | ||
NTMakefile | ||
README | ||
README-WINDOWS | ||
regen.sh |
AFS is a distributed file system that enables users to share and access all of the files stored in a network of computers as easily as they access the files stored on their local machines. The file system is called distributed for this exact reason: files can reside on many different machines, but are available to users on every machine. OpenAFS 1.0 was originally released by IBM under the terms of the IBM Public License 1.0 (IPL10). For details on IPL10 see the LICENSE file in this directory. The current OpenAFS distribution is licensed under a combination of the IPL10 and many other licenses as granted by the relevant copyright holders. The LICENSE file in this directory contains more details, thought it is not a comprehensive statement. See INSTALL for information about building and installing OpenAFS on various platforms. See CODING for developer information and guidelines. See NEWS for recent changes to OpenAFS.