From: Douglas Roark <joroark@vt.edu>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Python test suite failures (was Re: Planned Obsolescence)
Date: Sun, 18 Dec 2016 12:51:00 -0800 [thread overview]
Message-ID: <7f51525a-6aeb-e1cd-060c-2f7f34700b6b@vt.edu> (raw)
In-Reply-To: <d2e0dd76-e6ec-8ccb-5a33-48f0d005afe9@librelamp.com>
[-- Attachment #1.1: Type: text/plain, Size: 831 bytes --]
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.
--
---
Douglas Roark
Cryptocurrency, network security, travel, and art.
https://onename.com/droark
joroark@vt.edu
PGP key ID: 26623924
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next prev parent reply other threads:[~2016-12-18 20:51 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 ` Douglas Roark [this message]
2016-12-19 8:13 ` [bitcoin-dev] Python test suite failures (was Re: Planned Obsolescence) Alice Wonder
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=7f51525a-6aeb-e1cd-060c-2f7f34700b6b@vt.edu \
--to=joroark@vt.edu \
--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