00:02 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/70b12af87eb0...8ee572f0940b

00:02 < bitcoin-git> bitcoin/master c84ff23 fanquake: build: ignore macOS make deploy artefacts & add them to clean-local

00:02 < bitcoin-git> bitcoin/master 8ee572f fanquake: Merge #16371: build: ignore macOS make deploy artefacts & add them to clea...

00:03 < bitcoin-git> [bitcoin] fanquake merged pull request #16371: build: ignore macOS make deploy artefacts & add them to clean-local (master...ignore_osx_volname) https://github.com/bitcoin/bitcoin/pull/16371

00:31 < aj> BlueMatt: 420x100? blaze it!

00:39 < roconnor> Acutally this year I decided to adjust my coding width to 132 characters. I figure if it can fit on a VT100 can display it 132 characters on a line, that's good enough for me, punch card users be damned.

00:39 < roconnor> (er, my copyediting of that statment didn't really work out).

00:40 < fanquake> Travis initiating a crack-down or what: https://imgur.com/a/kIDI201

00:44 < aj> fanquake: their algorithms have realised you're a bot

00:48 < luke-jr> fanquake: they tend to do that; if you're runningTravis on your personal repo, get them to add it to the whitelist

00:48 < luke-jr> (although I guess they may insist we pay them more to retain the whitelist? :/)

03:29 < bitcoin-git> [bitcoin] fanquake opened pull request #16674: refactor: remove obsolete qt algorithm usage (master...remove_obselete_qt_usage) https://github.com/bitcoin/bitcoin/pull/16674

06:24 < fanquake> Travis-CI support have helpfully informed me that I'm probably mining cryptocurrency with their CI

06:25 < warren> fanquake: replace all strings to random strings, that'll fix it

07:26 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/8ee572f0940b...01ebaa05a487

07:26 < bitcoin-git> bitcoin/master 2dbfb37 Jeremy Rubin: Fix Char as Bool in interfaces

07:26 < bitcoin-git> bitcoin/master 01ebaa0 fanquake: Merge #16572: wallet: Fix Char as Bool in Wallet

07:27 < bitcoin-git> [bitcoin] fanquake merged pull request #16572: wallet: Fix Char as Bool in Wallet (master...fix-wallet-charbool) https://github.com/bitcoin/bitcoin/pull/16572

09:22 < provoostenator> fanquake: that happened to me as well as week ago. The most annoying part is that when Travis stops running on your PRs, Github doesn't mark that as CI failure.

09:22 < provoostenator> Emailing their support helped, though it took a day in my case.

12:06 < instagibbs> yeah they're pretty fast whitelisting

12:06 < instagibbs> took me a few hours to get back in

12:24 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/01ebaa05a487...6dfa9efa3f55

12:24 < bitcoin-git> bitcoin/master 6011c9d Jonas Schnelli: QA: fix rpc_setban.py race

12:24 < bitcoin-git> bitcoin/master 6dfa9ef MarcoFalke: Merge #16656: test: fix rpc_setban.py race

12:25 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #16656: test: fix rpc_setban.py race (master...2019/08/rpc_setban) https://github.com/bitcoin/bitcoin/pull/16656

13:33 < elichai2> People have talked about Github's CI, apperantly I got in to the beta, hope to try it soon and give feedback on how is it compared to Travis/Appveyor :)

13:41 < jonasschnelli> Good to know elichai2!

13:42 < elichai2> OS wise the docs says they support Windows Server 2019/Windows Server 2016 R2/Ubuntu 18.04/Ubuntu 16.04/macOS X Mojave 10.14

16:05 < stevenroose> I'm trying to run Core's functional test suite of the 0.18 branch for Elements (I made the few changes to address the correct binaries and directories etc). I'm getting this error:

16:05 < stevenroose> test_framework.test_node.FailedToStartError: [node 0] bitcoind exited with status -11 during initialization

16:06 < stevenroose> Which is super strange. -11 is RPC_WALLET_INVALID_LABEL_NAME.

16:06 < phantomcircuit> stevenroose, your question is out of scope for this channel

16:06 < stevenroose> Which is only invoked when getnewaddress, setlabel, getreceivedbylabel, addmultisigaddress or getaddressesbylabel is called.

16:07 < stevenroose> Well, my question was gonna be if the test_framework code ever invokes any of those RPC methods.

16:07 < stevenroose> I grep'd only found getnewaddress but never with a label attached.

16:09 < stevenroose> phantomcircuit: sorry if this is out of scope.. nvm them. just puzzled how I could get a RPC_WALLET_INVALID_LABEL_NAME by invoking create_cache.py

16:56 < jnewbery> stevenroose: RPC_WALLET_INVALID_LABEL_NAME is a JSON error returned by RPC methods. It's not an exit code for the bitcoind binary

17:21 < provoostenator> Also note that a lot of non-wallet tests do use a wallet.

19:44 < MarcoFalke> [12:05] <stevenroose> test_framework.test_node.FailedToStartError: [node 0] bitcoind exited with status -11 during initialization

19:44 < MarcoFalke> This is not an RPC error, but the exit code of bitcoind

19:45 < MarcoFalke> Usually a segfault, assertion error, InitError, ...

19:45 < MarcoFalke> runtime_error, ...