pgbackrest.git / summary / log / commit / refs

commit    80a770ed2ea8d060d8ea77dabb239cf7e861774d
Author:   David Steele <david@pgmasters.net>
Date:     Sat Oct 24 15:16:06 2020 +0000

    Clarify intended usage of harnessCfgLoadRaw().


test/src/common/harnessConfig.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/test/src/common/harnessConfig.h b/test/src/common/harnessConfig.h index d489e9a87..c7270add2 100644 --- a/test/src/common/harnessConfig.h +++ b/test/src/common/harnessConfig.h @@ -13,7 +13,8 @@ Load a test configuration without any side effects There's no need to open log files, acquire locks, reset log levels, etc. ***********************************************************************************************************************************/ -// Low-level version used in a few places to simulate special cases and error conditions. Most tests should use harnessCfgLoad(). +// Low-level version used when it is important that only the options set explicity by the test are present in the config. The +// additional options set by harnessCfgLoad() can make these tests harder to write. Most tests should use harnessCfgLoad(). void harnessCfgLoadRaw(unsigned int argListSize, const char *argList[]); // Automatically adds the exe, command (and role), lock-path, and log-path so executing the binary works locally or in a container. [parent: 76cfd8ca703f]