a7444a92b9
- The ProcessMessages signal was scheduling/connecting its slots slightly out of order for what we need - First, the scan_messages needs to run and copy out the stream - Second, Bitcoin's ProcessMessages needs to run in order to run AcceptToMemoryPool - Third, scan_messages_after needs to run in order to signal our tx_monitor - In order to make this happen, we need to pair ProcessMessages slot to the scan_messages slot and order that - Then, AFTER those two complete, we can schedule scan_messages_after
18 lines
426 B
YAML
18 lines
426 B
YAML
sudo: false
|
|
language: node_js
|
|
env:
|
|
- BITCORENODE_ENV=test BITCORENODE_ASSUME_YES=true
|
|
node_js:
|
|
- "v0.12.7"
|
|
before_install:
|
|
- git config --global user.email "dev@bitpay.com"
|
|
- git config --global user.name "BitPay, Inc."
|
|
script:
|
|
- _mocha -R spec integration/regtest.js
|
|
- _mocha -R spec integration/regtest-node.js
|
|
- _mocha -R spec integration/p2p.js
|
|
- _mocha -R spec --recursive
|
|
cache:
|
|
directories:
|
|
- cache
|