1 2018-05-25 04:09:16 0|fanquake|MarcoFalke Did you untag some PRs that had "Need Backport" tags? I'm sure there were more than 4 yesterday..
2 2018-05-25 04:10:33 0|fanquake|Yea, like #13192. If your untagging PRs, could you comment as to why they no-longer need backport?
3 2018-05-25 04:10:35 0|gribble|https://github.com/bitcoin/bitcoin/issues/13192 | [tests] Fixed intermittent failure in p2p_sendheaders.py. by lmanners ÷ Pull Request #13192 ÷ bitcoin/bitcoin ÷ GitHub
4 2018-05-25 13:17:19 0|promag|wumpus: MarcoFalke: should tag #13160 bugfix?
5 2018-05-25 13:17:21 0|gribble|https://github.com/bitcoin/bitcoin/issues/13160 | wallet: Unlock spent outputs by promag ÷ Pull Request #13160 ÷ bitcoin/bitcoin ÷ GitHub
6 2018-05-25 15:44:11 0|provoostenator|Friday chart fun at #12404
7 2018-05-25 15:44:14 0|gribble|https://github.com/bitcoin/bitcoin/issues/12404 | Prune more aggressively during IBD by Sjors ÷ Pull Request #12404 ÷ bitcoin/bitcoin ÷ GitHub
8 2018-05-25 15:47:46 0|ZiNC|Is it going to be merged for 0.16.1?
9 2018-05-25 15:52:50 0|luke-jr|provoostenator: is that based on EC2 measurements? if so, it's just noise to me
10 2018-05-25 15:54:13 0|provoostenator|It is. I (or someone else) can try to reproduce on a physical machine. I think it's too consistent to be jus noise though.
11 2018-05-25 15:55:12 0|provoostenator|These machines were running for almost a week; you'd expect other tenants to come and go.
12 2018-05-25 15:55:29 0|luke-jr|provoostenator: I suggest a raspi ;)
13 2018-05-25 15:55:43 0|provoostenator|The cache usage of course is deterministic.
14 2018-05-25 15:55:51 0|luke-jr|but you may have a point there
15 2018-05-25 15:56:26 0|provoostenator|I actually ordered 2x Orange Pi Plus 2E and 1x Nanopi Neo Plus 2...
16 2018-05-25 15:56:58 0|provoostenator|2 GB and 1 GB RAM respectively. Afaik both slightly better than the lastest Rasperry Pi, and not much more expensive.
17 2018-05-25 15:58:43 0|ZiNC|Does the prune size affect the behavior?
18 2018-05-25 15:58:47 0|provoostenator|Regarding EC2, just for comparison, the i3.2xlarge, which has a large enough SSD drive to avoid pruning and enough memory to max dbcache, just did a full IBD in 4 hours.
19 2018-05-25 16:00:08 0|provoostenator|A similar machine, but with pruning (on master), took about twice as long, but I haven't done an exact comparison.
20 2018-05-25 16:01:23 0|provoostenator|So for a project I'm working on, I just spin up a big machine, do the IBD, manually prune at the end and then downgrade.
21 2018-05-25 16:03:01 0|provoostenator|That costs about $4
22 2018-05-25 16:05:09 0|provoostenator|luke-jr: without more data I'd prefer to merge your variant to be on the safe side
23 2018-05-25 16:06:00 0|luke-jr|can always improve later
24 2018-05-25 16:07:38 0|provoostenator|Yeah, it might be worth trying more aggressive prunes again once we find a way to keep more of the cache in memory.
25 2018-05-25 19:33:52 0|bitcoin-git|[13bitcoin] 15jhfrontz opened pull request #13320: Ensure gitian-build.sh uses bash (06master...06patch-1) 02 https://github.com/bitcoin/bitcoin/pull/13320
26 2018-05-25 22:52:25 0|jhfrontz|I'm trying to do a Gitian build of Bitcoin Core on a stock (just installed from a liveUSB) Ubuntu 18.04 distro using the instructions at https://github.com/bitcoin-core/docs/blob/master/gitian-building.md#initial-gitian-setup . I keep running into situations where gitian-build.sh (or one of the scripts it calls) need to do some sort of interactive edits (e.g.., asking for confirmation on a package installation/customization
27 2018-05-25 22:52:25 0|jhfrontz|nd the script inevitably fails.
28 2018-05-25 22:53:26 0|jhfrontz|I'm assuming I'm missing some bootstrapping (that isn't otherwise handled by the build script). But maybe it's not even supposed to work on Ubuntu?
29 2018-05-25 22:54:39 0|sipa|it's certainly supposed to work on ubuntu
30 2018-05-25 22:54:53 0|sipa|but ubuntu 18.04 is pretty recent; maybe people haven't gone through it
31 2018-05-25 22:55:58 0|jhfrontz|Hmm, ok. Is there a better/stabler Ubuntu version that stands a higher probability of succeeding?
32 2018-05-25 22:56:52 0|jhfrontz|17.10 says it's from Oct 2017.
33 2018-05-25 22:57:50 0|sipa|yes, the version numbers are YY.MM :)
34 2018-05-25 22:58:03 0|jhfrontz|hah, ok, tnx
35 2018-05-25 22:59:28 0|sipa|travis uses trusty (14.04)
36 2018-05-25 23:01:08 0|jhfrontz|ok, I'll try that; thanks!
37 2018-05-25 23:08:52 0|ken2812221|jhfrontz: If you are using lxc 3.0, you'll need to apply PR#178 of gitian-builder.
38 2018-05-25 23:08:54 0|gribble|https://github.com/bitcoin/bitcoin/issues/178 | Link with libpthread on Linux, required by libboost_thread. by wizeman ÷ Pull Request #178 ÷ bitcoin/bitcoin ÷ GitHub
39 2018-05-25 23:11:18 0|ken2812221|And modify /etc/default/lxc-net, replace "lxcbr0" to "br0"