| commit | 3fae7ad96d89e670a75b1335824c8ad3a92c8db0 | |
| author | SZEDER Gábor <szeder.dev@gmail.com> | |
| Wed, 13 Mar 2019 12:24:18 +0000 (13 13:24 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 14 Mar 2019 03:34:39 +0000 (14 12:34 +0900) | ||
| tree | 94430b753c09b1167469b0db515e37c4e0a8873e | treesnapshot (tar.gz zip) |
| parent | 0e67c32955cee24c5ff534dd3f5f0de58ba91d02 | commitdiff |
git p4 test: disable '-x' tracing in the p4d watchdog loop
According to the comments in 't/lib-git-p4.sh', sometimes 'p4d' seems
to hang, and to deal with that 'start_p4d' starts a watchdog process
to kill it after a long-enough timeout ($P4D_TIMEOUT, defaults to
300s). This watchdog process is implemented as a background subshell
loop iterating once every second until the timeout expires, producing
a few lines of trace output on each iteration when the test script is
run with '-x' tracing enabled. The watchdog loop's trace gets
intermixed with the real test output and trace, and makes that harder
to read.
Send the trace output of this loop to /dev/null to avoid polluting the
real test output.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
According to the comments in 't/lib-git-p4.sh', sometimes 'p4d' seems
to hang, and to deal with that 'start_p4d' starts a watchdog process
to kill it after a long-enough timeout ($P4D_TIMEOUT, defaults to
300s). This watchdog process is implemented as a background subshell
loop iterating once every second until the timeout expires, producing
a few lines of trace output on each iteration when the test script is
run with '-x' tracing enabled. The watchdog loop's trace gets
intermixed with the real test output and trace, and makes that harder
to read.
Send the trace output of this loop to /dev/null to avoid polluting the
real test output.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/lib-git-p4.sh | diffblobblamehistory |