AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

QTestLib: allow for non-zero values in env variables

Browse Source 
The usual behavior for env variables is that any nonzero
value means "enable", so do the same for a couple of QTestLib
env vars. While at it: document them.

Change-Id: I854285df5d7af5be771f9d6532ddec5d8a6f8987
Pick-to: 6.0
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
This commit is contained in:
Giuseppe D'Angelo 2020-12-03 00:10:39 +01:00
parent a7610a0cf7
commit 89def082c6
2 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/testlib/doc/src/qttestlib-manual.qdoc
View File

@ -362,6 +362,20 @@
Outputs the possible command line arguments and gives some useful help.
\endlist
\section1 Qt Test Environment Variables
You can set certain environment variables in order to affect
the execution of an autotest:
\list
\li \c QTEST_DISABLE_CORE_DUMP \br
Setting this variable to a non-zero value will disable the generation
of a core dump file.
\li \c QTEST_DISABLE_STACK_DUMP \br
Setting this variable to a non-zero value will prevent Qt Test from
printing a stacktrace in case an autotest times out or crashes.
\endlist
\section1 Creating a Benchmark
To create a benchmark, follow the instructions for creating a test and then add a

4
src/testlib/qtestcase.cpp
View File

@ -190,7 +190,7 @@ static void disableCoreDump()
{
bool ok = false;
const int disableCoreDump = qEnvironmentVariableIntValue("QTEST_DISABLE_CORE_DUMP", &ok);
if (ok && disableCoreDump == 1) {
if (ok && disableCoreDump) {
#if defined(Q_OS_UNIX) && !defined(Q_OS_INTEGRITY)
struct rlimit limit;
limit.rlim_cur = 0;
@ -206,7 +206,7 @@ static void stackTrace()
{
bool ok = false;
const int disableStackDump = qEnvironmentVariableIntValue("QTEST_DISABLE_STACK_DUMP", &ok);
if (ok && disableStackDump == 1)
if (ok && disableStackDump)
return;
if (debuggerPresent() || hasSystemCrashReporter())