slackcoder/bitcoin - Bitcoin Code integration/staging tree

Age	Commit message (Collapse)	Author
2018-10-24	qa: Run all tests even if wallet is not compiled	MarcoFalke
	Github-Pull: #14180 Rebased-From: fac95398366f644911b58f1605e6bc37fb76782d
2018-09-06	test: Add test for config file parsing errors	MarcoFalke
	Github-Pull: #14105 Rebased-From: ed2332aeffb071a3404be9cff8f9fb8a81a9fbfb Tree-SHA512: 17fa88a2848f1c9c9c8a127b5ea4c45761ce8e06a609dd40f8e90bb9117d88c9d2c81e752c9c0f1a44ecadbb5bedd2973bc4548da2a6d463c789797191e85ab1
2018-07-27	Update copyright headers to 2018	DrahtBot

2018-07-17	qa: Temporarily disable test that reads the default datadir location	MarcoFalke

2018-04-11	[tests] Use regtest section in functional tests configs	Anthony Towns

2018-04-01	qa: Match full plain text by default	MarcoFalke

2018-03-22	Merge #12076: qa: Use node.datadir instead of tmpdir in test framework	Wladimir J. van der Laan
	c8330d4 qa: Use node.datadir instead of tmpdir in test framework (MarcoFalke) Pull request description: Commit c53c9831eedaf3b311bb942945268830f9ba3abc introduced the utility function `get_datadir_path`, however not all places in the code use this util function. Using the util function everywhere makes it easier to review pull requests related to the datadir. This commit replaces datadir path creation with the `datadir` member of `TestNode`, which itself uses `get_datadir_path`. Tree-SHA512: c75707ab7149d732a6d56152a5813138a33459d3d07577b60b89f2a207c83b7663fac5f203593677c9892d1c23a5eba4bd45c5c4ababf040d720b437240fcddf
2018-03-19	qa: Use node.datadir instead of tmpdir in test framework	MarcoFalke

2018-03-18	[Tests] Require exact match in assert_start_raises_init_eror()	John Newbery

2018-03-18	[Tests] Move assert_start_raises_init_error method to TestNode	John Newbery

2018-03-03	Create new wallet databases as directories rather than files	Russell Yanofsky
	This change should make it easier for users to make complete backups of wallets because they can now just back up the specified `-wallet=<path>` path directly, instead of having to back up the specified path as well as the transaction log directory (for incompletely flushed wallets). Another advantage of this change is that if two wallets are located in the same directory, they will now use their own BerkeleyDB environments instead using a shared environment. Using a shared environment makes it difficult to manage and back up wallets separately because transaction log files will contain a mix of data from all wallets in the environment.
2018-01-25	[tests] Rename feature_* functional tests.	Anthony Towns