Browse Source
I don't remember ever seeing a bug which only showed up in VALGRIND=1 with developer mode disabled, so don't test that, and spread out the other test more evenly. In addition, disable the worst-performing tests in DEVELOPER=0 mode. Here timings from my build machine: the worst 6 (- DEVELOPER=0 VALGRIND=0) with the same tests (+ DEVELOPER=1 VALGRIND=1) -452.42s call tests/test_pay.py::test_channel_spendable +87.69s call tests/test_pay.py::test_channel_spendable -335.66s call tests/test_gossip.py::test_gossip_store_compact_on_load +47.41s call tests/test_gossip.py::test_gossip_store_compact_on_load -332.07s call tests/test_connection.py::test_opening_tiny_channel +89.71s call tests/test_connection.py::test_opening_tiny_channel -331.97s call tests/test_pay.py::test_channel_spendable_large +56.23s call tests/test_pay.py::test_channel_spendable_large -305.28s call tests/test_invoices.py::test_invoice_routeboost +37.57s call tests/test_invoices.py::test_invoice_routeboost -284.28s call tests/test_plugin.py::test_htlc_accepted_hook_forward_restart +49.12s call tests/test_plugin.py::test_htlc_accepted_hook_forward_restart Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>pull/2938/head
Rusty Russell
5 years ago
3 changed files with 14 additions and 10 deletions
Loading…
Reference in new issue