public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alice Wonder <alice@librelamp.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Python test suite failures (was Re: Planned Obsolescence)
Date: Mon, 19 Dec 2016 00:13:51 -0800	[thread overview]
Message-ID: <a5f216cb-7a06-a52f-c132-9fc5dcba138e@librelamp.com> (raw)
In-Reply-To: <7f51525a-6aeb-e1cd-060c-2f7f34700b6b@vt.edu>

On 12/18/2016 12:51 PM, Douglas Roark via bitcoin-dev wrote:
> On 2016/12/18 12:07, Alice Wonder via bitcoin-dev wrote:
>> I almost did not update to 0.13.0 because the test suite was failing due
>> to python errors. How to fix them was posted on bitcointalk.
>>
>> 0.13.1 came with new python errors in the test suite. So I just said
>> fuck it.
>>
>> When the test suite actually works in my fairly standard environment
>> (CentOS) in the distributed release, I will upgrade.
>
> Can you post more info about the problems you're seeing, how you fixed
> them, your environment, etc., or at least post an issue on Github? I'm
> sure somebody would be happy to help. Some info on how to reproduce the
> problems would be very helpful. :)
>
> Thanks.

For 0.13.0 I had to do

export LANG=en_US.utf8

before running the test suite. I build in clean chroot build environment 
to avoid accidental linking to non-standard libraries, and in that 
environment the LANG is normally set to C as LANG normally doesn't 
matter for compiling software that is expected to run regardless of what 
the LANG is.

That I believe was fixed in 0.13.1.

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'
make[3]: *** [check-local] Error 1
make[3]: Leaving directory `/builddir/build/BUILD/bitcoin-0.13.1/src'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/builddir/build/BUILD/bitcoin-0.13.1/src'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/builddir/build/BUILD/bitcoin-0.13.1/src'
make: *** [check-recursive] Error 1

0.13.0 test works just fine (once the LANG is set to something utf8)


  reply	other threads:[~2016-12-19  8:14 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 [this message]
2016-12-21 18:33         ` Marco Falke
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=a5f216cb-7a06-a52f-c132-9fc5dcba138e@librelamp.com \
    --to=alice@librelamp.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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