< Victorsueca> BlueMatt: wut? 0.14.0rc1 so fast?
<@wumpus> he doesn't mean tagging the release
< Victorsueca> ahh
< Victorsueca> the milestone ok
< Victorsueca> just woke up :P
< Victorsueca> morning btw
< Victorsueca> have some free time now, is there anything important that needs to be tested on windows?
< 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.
< 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
< 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.
< fanquake> Sure, this list will show you the current "big" changes for the 0.14.0 release: https://github.com/bitcoin/bitcoin/milestone/21
< Victorsueca> nice
< achow101> where in the code is a transaction determined to be related to the wallet?
< 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
< sipa> achow101: IsMine
< sipa> achow101: called from AddToWalletIfInvolvingMe
< achow101> thanks
< luke-jr> I don't think that's my fault? O.o
< Victorsueca> lol
< Victorsueca> rlly? travis failed because of a image?
< luke-jr> on rpc tests nonetheless
< sipa> sometimes tests fail randomly
< luke-jr> I thought those were fixed :<
< jonasschnelli> There is always one more to fix...
< Victorsueca> probably it's just travis gets hiccup sometimes and when so happens lots of tests crash
< arubi> "OSError: [Errno 98] Address already in use", means some previous test's node didn't shut down and is using the ip+port ?
< sipa> arubi: seems likely
< 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
< arubi> I mean, `ping`, this is usually configured out of the box, maybe travis' images behave the same
< 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
< 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
< 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