Open UncleHunto opened 7 years ago
Not surprising. Most likely these began failing because your system clock is now past Aug 1.
I'll investigate fixing it more in a few days unless someone else gets to it first.
Note this is a bug in the tests, not the node itself - running UASF/bitcoin should still be safe.
Describe the issue
Some of the make check tests are failing with a "bad-no-segwit" message. I have included the contents of my test-suite.log file for further details
Can you reliably reproduce the issue?
Yes
If so, please list the steps to reproduce below:
Expected behaviour
Tell us what should happen All tests should be passed.
Actual behaviour
Tell us what happens instead One test failed.
What version of bitcoin-core are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
Arch AUR package: bitcoin-uasf-git v0.14.2.uasfsegwit1.0.r0.g2e7690fc8-1-x86_64
Machine specs:
Any extra information that might be useful in the debugging process.
This is normally the contents of a
debug.log
orconfig.log
file. Raw text or a link to a pastebin type site are preferred.