From: Marco Falke <marco.falke@tum•de>
To: Alice Wonder <alice@librelamp•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Python test suite failures (was Re: Planned Obsolescence)
Date: Wed, 21 Dec 2016 19:33:14 +0100 [thread overview]
Message-ID: <CAK51vgDDR__ZTtK3kbu3peKpiVyL=_PskBBDbt1mQ7z+qpKd_g@mail.gmail.com> (raw)
In-Reply-To: <a5f216cb-7a06-a52f-c132-9fc5dcba138e@librelamp.com>
> In 0.13.1 the error is
>
>
> Running test/bitcoin-util-test.py...
> Traceback (most recent call last):
> File "./test/bitcoin-util-test.py", line 12, in <module>
> "bitcoin-util-test.json",buildenv)
> File "/builddir/build/BUILD/bitcoin-0.13.1/src/test/bctest.py", line 54,
> in bctester
> bctest(testDir, testObj, buildenv.exeext)
> File "/builddir/build/BUILD/bitcoin-0.13.1/src/test/bctest.py", line 26,
> in bctest
> outputData = open(testDir + "/" + outputFn).read()
> FileNotFoundError: [Errno 2] No such file or directory:
> './test/data/blanktx.json'
This was a known problem on the *master* branch. If you still
encounter any issues on the current 0.13.2 release candidate, please
let us know in https://github.com/bitcoin/bitcoin/issues/9394. (Make
sure to include the version of centos you are running)
next prev parent reply other threads:[~2016-12-21 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f27bd300c20d1b48cddc7e1d1dc1a96c@112bit.com>
2016-12-15 3:38 ` [bitcoin-dev] Planned Obsolescence jg
2016-12-15 18:12 ` Aymeric Vitte
2016-12-15 18:48 ` Jorge Timón
2016-12-15 22:25 ` Angel Leon
2016-12-15 22:44 ` Ethan Heilman
2016-12-18 10:34 ` Matt Corallo
2016-12-18 20:50 ` Chris Riley
2016-12-18 20:07 ` Alice Wonder
2016-12-18 20:51 ` [bitcoin-dev] Python test suite failures (was Re: Planned Obsolescence) Douglas Roark
2016-12-19 8:13 ` Alice Wonder
2016-12-21 18:33 ` Marco Falke [this message]
2016-12-19 2:22 ` [bitcoin-dev] Planned Obsolescence Matt Corallo
2016-12-19 6:39 ` Btc Drak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK51vgDDR__ZTtK3kbu3peKpiVyL=_PskBBDbt1mQ7z+qpKd_g@mail.gmail.com' \
--to=marco.falke@tum$(echo .)de \
--cc=alice@librelamp$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox