07:12 < Victorsueca> BlueMatt: wut? 0.14.0rc1 so fast?

07:13 <@wumpus> he doesn't mean tagging the release

07:14 < Victorsueca> ahh

07:14 < Victorsueca> the milestone ok

07:14 < Victorsueca> just woke up :P

07:14 < Victorsueca> morning btw

10:20 < Victorsueca> have some free time now, is there anything important that needs to be tested on windows?

11:28 < fanquake> Victorsueca If you'd just like to test stuff in general, start here : https://github.com/bitcoin/bitcoin/issues?q=is%3Aopen+is%3Aissue+label%3AWindows . See if you can recreate/investigate issues. If so post some info about the system your using, how you tested it etc.

11:30 < Victorsueca> I was thinking on testing more specific stuff, specifically the issues or PRs that you think are more important to be tested at the moment

11:31 < fanquake> There are no Windows specific pull requests open at the moment, but some easier things to start testing are PRs with the GUI label. Even just posting screenshots of how GUI changes look on Windows, given we rarely get that.

11:31 < fanquake> Sure, this list will show you the current "big" changes for the 0.14.0 release: https://github.com/bitcoin/bitcoin/milestone/21

11:32 < Victorsueca> nice

18:44 < achow101> where in the code is a transaction determined to be related to the wallet?

18:46 < bitcoin-git> [bitcoin] luke-jr opened pull request #9150: Qt: Make network disabled icon larger and 50% opaque (master...gui_netdisabled_icon_enlarge) https://github.com/bitcoin/bitcoin/pull/9150

18:51 < sipa> achow101: IsMine

18:51 < sipa> achow101: called from AddToWalletIfInvolvingMe

18:51 < achow101> thanks

19:33 < * luke-jr> peers at Travis https://github.com/bitcoin/bitcoin/pull/9150

19:33 < luke-jr> I don't think that's my fault? O.o

19:39 < Victorsueca> lol

19:39 < Victorsueca> rlly? travis failed because of a image?

19:40 < luke-jr> on rpc tests nonetheless

19:42 < sipa> sometimes tests fail randomly

19:42 < luke-jr> I thought those were fixed :<

19:44 < jonasschnelli> There is always one more to fix...

19:48 < Victorsueca> probably it's just travis gets hiccup sometimes and when so happens lots of tests crash

19:49 < arubi> "OSError: [Errno 98] Address already in use", means some previous test's node didn't shut down and is using the ip+port ?

19:54 < sipa> arubi: seems likely

19:57 < arubi> sipa, reason I'm asking is because I've been burned before by trying to manage ports for a bunch of nodes with different uses for tests, and eventually I'm now only using the default ports for all running nodes, but different IPs on the 127.x.x.x range, so mainnet is on 127.0.0.x, testnet on 127.0.1.x, regtest 127.0.3.x ... maybe if for each node that runs, the IP is incremented, then this wouldn't happen

19:58 < arubi> I mean, `ping 127.200.192.12`, this is usually configured out of the box, maybe travis' images behave the same

21:33 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9151: [qa] proxy_test: Calculate hardcoded port numbers (master...Mf1611-qaPort) https://github.com/bitcoin/bitcoin/pull/9151

21:54 < bitcoin-git> [bitcoin] luke-jr closed pull request #9150: Qt: Make network disabled icon larger and 50% opaque (master...gui_netdisabled_icon_enlarge) https://github.com/bitcoin/bitcoin/pull/9150

22:08 < bitcoin-git> [bitcoin] luke-jr opened pull request #9152: Wallet/RPC: sweepprivkeys method to scan UTXO set and send to local wallet (master...sweepprivkeys) https://github.com/bitcoin/bitcoin/pull/9152