Gavin Andresen dbca89b74b Trigger -alertnotify if network is upgrading without you ... This adds a -regetest-only undocumented (for regression testing only) command-line option -blockversion=N to set block.nVersion. Adds to the "has the rest of the network upgraded to a block.nVersion we don't understand" code so it calls -alertnotify when 51 of the last 100 blocks are up-version. But it only alerts once, not with every subsequent new, upversion block. And adds a forknotify.py regression test to make sure it works. Tested using forknotify.py: Before adding CAlert::Notify, get: Assertion failed: -alertnotify did not warn of up-version blocks Before adding code to only alert once: Assertion failed: -alertnotify excessive warning of up-version blocks After final code in this pull: Tests successful		2014-10-09 10:28:27 -04:00
..
build-tests.sh.in	Trigger -alertnotify if network is upgrading without you	2014-10-09 10:28:27 -04:00
pull-tester.py	Add licenses for tests and test data	2014-03-18 10:20:55 +01:00
pull-tester.sh	stop bitcoind/bitcoin-cli processes that might have been left running	2014-05-02 12:37:20 -04:00
run-bitcoind-for-test.sh.in	travis: If the comparison-tool fails, dump the tail of the debug log	2014-10-01 16:47:33 -04:00