diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-05-07 07:56:30 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-05-07 07:56:33 -0400 |
| commit | c1cd2b5a97f435b75f860a1a4d95e15a2c3b270b (patch) | |
| tree | 121ef4713f1e7d01a386e2b51bdc5d5b438d1bc8 /test/functional/p2p_invalid_messages.py | |
| parent | 3b1e289248dcda896aaa1c84995ee9c6077601e6 (diff) | |
| parent | fa082d0a57afedca9122fac4aecd6a3070f06b04 (diff) | |
Merge #18899: travis: Remove valgrind
fa082d0a57afedca9122fac4aecd6a3070f06b04 travis: Remove valgrind (MarcoFalke)
Pull request description:
When the valgrind run was added, it took 2 hours. Travis kindly raised the timeout limit to the maximum possible of 3 hours.
Today, a full build of Bitcoin Core with all tests takes more than three hours. Thus, it is impossible to run all tests on travis.
Moreover, the feedback loop for developers that create a pull request takes at least 2 hours, but in some cases (when the travis queue is full) until the next day. This is unacceptable.
Fix both issues by removing the build from travis.
Please note that the `ci/test/` configurations are *not* removed. They will stay in the repo and can be executed anywhere (just not on travis).
ACKs for top commit:
jamesob:
ACK https://github.com/bitcoin/bitcoin/pull/18899/commits/fa082d0a57afedca9122fac4aecd6a3070f06b04
jnewbery:
utACK fa082d0a57afedca9122fac4aecd6a3070f06b04
Tree-SHA512: 9acaa0e2d3926014fadb7dd2e86c4e01df382e9399f6ae99f989fa609da66a77bdd1b75d6ff42d2686f38f730b8564e6dc722aa597a473290c9d30c2abe7ef0f
Diffstat (limited to 'test/functional/p2p_invalid_messages.py')
0 files changed, 0 insertions, 0 deletions