aboutsummaryrefslogtreecommitdiff
path: root/qa/rpc-tests/forknotify.py
Commit message (Collapse)AuthorAgeFilesLines
* Remove unused Python variablespracticalswift2017-01-131-1/+1
|
* test: Explicitly set encoding to utf8 when opening text filesWladimir J. van der Laan2016-09-291-3/+3
| | | | | | | | | | | | | | These are text files but their encoding does not depend on the locale. Not all of them require utf8 but it is better to fix it at something to remove potential unpredictability. This is necessary on FreeBSD where no locale is set by default, and apparently Python defaults not only the terminal encoding to the locale but that of every text file. So without LOCALE environment it defaults text file encoding to ASCII. This causes problems with e.g. `bitcoin.conf`. Luckily the locale doesn't affect the default encoding for str.encode() and bytes.decode() on Python 3, so this is the only change necessary.
* [qa] Remove hardcoded "4 nodes" from test_frameworkMarcoFalke2016-05-151-0/+5
|
* [qa] Switch to py3MarcoFalke2016-05-051-2/+2
|
* [qa] Fix pyton syntax in rpc testsMarcoFalke2016-01-131-2/+0
|
* Bump copyright headers to 2015MarcoFalke2015-12-131-1/+1
|
* [QA] restructure rpc tests directoryJonas Schnelli2015-05-181-3/+2
| | | | * move non-test classes to subdir `test-framework`
* Introduce separate 'generate' RPC callPieter Wuille2015-04-011-4/+4
|
* Fix python usage for arch's broken maintainersMatt Corallo2014-11-271-1/+1
|
* tests: fix forknotify.py on windowsCory Fields2014-10-311-1/+1
| | | | | Windows interprets 'foo.txt' as a literal filename while "foo.txt" is treated as expected.
* Merge pull request #5121Wladimir J. van der Laan2014-10-271-1/+1
|\ | | | | | | 214091d Update license in pull-tester and rpc-tests (Michael Ford)
| * Update license in pull-tester and rpc-testsMichael Ford2014-10-231-1/+1
| | | | | | | | Add missing copyright/license header where necessary
* | Extend getchaintips RPC test.Daniel Kraft2014-10-241-18/+17
|/ | | | | Add the capability to simulate network splits to the RPC test framework and use it to do more extensive testing of 'getchaintips'.
* Trigger -alertnotify if network is upgrading without youGavin Andresen2014-10-091-0/+65
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