Setting the TIMEOUT environment variable has been a noop in both cases since its introduction.
It seems to have been inadvertently copy-pasted from existed code. For example, in commit d80e3cbece857b293a4903ef49c4d543bb2cfb7f, it was needlessly copied from a valid case a few lines above for the qa/pull-tester/run-bitcoind-for-test.sh script.
Setting the `TIMEOUT` environment variable has been a noop in both cases
since its introduction.
It seems to have been inadvertently copy-pasted from existing code. For
example, in commit d80e3cbece857b293a4903ef49c4d543bb2cfb7f, it was
needlessly copied from a valid case a few line above for the
`qa/pull-tester/run-bitcoind-for-test.sh` script.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | maflcko, edilmedeiros |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
utACK 189d0da3f6f561c808fdd9fbd4dfd34ccfa23fe1
ACK 189d0da3f6f561c808fdd9fbd4dfd34ccfa23fe1
Kind of tested with
❯ ./configure --with-boost=/opt/local/libexec/boost/1.78 --disable-wallet --with-gui=no --disable-gui-tests --disable-zmq --disable-man --without-bdb --enable-lcov
❯ make -j11 cov
which I guess would cover the functional_test.info rule.