Bitcoin Core integration/staging tree
Clone or download
sipa Merge #14465: tests: Stop node before removing the notification file
ca6d86c tests: Stop node before removing the notification file (Chun Kuan Lee)

Pull request description:

  Stop node before removing the notification file to make sure the command has been terminated. After then we could removing those files safely and do not receive any permission error. (See #14446)

  The permission error is Windows specific, documented in python doc:
  >On Windows, attempting to remove a file that is in use causes an exception to be raised

  See https://docs.python.org/3/library/os.html#os.remove

Tree-SHA512: fbdabf3a9a838bb59ba207dd9e9fbdd87c702a99ad66bee0b2b1537f80f8630d22d9d5e9c4ded23a82a66bfc10989227fb024b27393425abe0e5a2ad4e4cbb82
Latest commit d387507 Oct 19, 2018
Permalink
Failed to load latest commit information.
.github doc: Add GitHub pr template Sep 23, 2018
.travis build: Pin to specific versions of Python packages we install from Py… Oct 16, 2018
.tx tx: Update transifex slug 016x→017x Aug 2, 2018
build-aux/m4 Merge #13095: build: update ax_boost_chrono/unit_test_framework Jul 26, 2018
build_msvc Merge #14146: wallet: Remove trailing separators from -walletdir arg Oct 18, 2018
contrib [gitian] use versioned unsigned tarballs instead of generically named… Sep 26, 2018
depends Merge #14385: depends: qt: avoid system harfbuzz and bz2 Oct 8, 2018
doc Merge #14291: wallet: Add ListWalletDir utility function Oct 18, 2018
share Merge #14018: Bugfix: NSIS: Exclude Makefile* from docs Aug 22, 2018
src Merge #14291: wallet: Add ListWalletDir utility function Oct 18, 2018
test Merge #14465: tests: Stop node before removing the notification file Oct 19, 2018
.appveyor.yml appveyor: trivial build cache modifications Oct 5, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore [build] .gitignore: add QT Creator artifacts Dec 22, 2017
.travis.yml qa: Run more tests with wallet disabled Sep 25, 2018
CONTRIBUTING.md doc: add note to contributor docs about warranted PR's Jul 30, 2018
COPYING [Trivial] Update license year range to 2018 Dec 31, 2017
INSTALL.md Update INSTALL landing redirection notice for build instructions. Oct 5, 2016
Makefile.am Merge #14253: Build: during 'make clean', remove some files that are … Oct 8, 2018
README.md doc: Adjust bitcoincore.org links Jul 22, 2018
autogen.sh Add "export LC_ALL=C" to all shell scripts Jun 14, 2018
configure.ac configure: Make it possible to build only one of bitcoin-cli or bitco… Sep 13, 2018
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes Dec 14, 2015

README.md

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/, or read the original whitepaper.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.