< GitHub163> [bitcoin] kazcw closed pull request #8147: CNodeState encapsulation, lock reduction (master...cs_misbehavior) https://github.com/bitcoin/bitcoin/pull/8147
< jonasschnelli> Do we link libdbus dynamic for our gitian builds?
<@wumpus> jonasschnelli: I think qt will always dlopen it at run time
<@wumpus> AFAIK we don't link to libdbus at all
< GitHub135> [bitcoin] laanwj opened pull request #8213: gitian: Move as-root preparation to gitian prepare script (master...2016_06_gitian_linux_prepare_script) https://github.com/bitcoin/bitcoin/pull/8213
< GitHub10> [bitcoin] MarcoFalke opened pull request #8214: [qa] mininode: fail on send_message instead of silent return (master...Mf1606-qaMininodeAssert) https://github.com/bitcoin/bitcoin/pull/8214
< GitHub94> [bitcoin] MarcoFalke opened pull request #8215: [wallet] tests: Don't use floating point (master...Mf1606-walletTestFloat) https://github.com/bitcoin/bitcoin/pull/8215
< GitHub191> [bitcoin] MarcoFalke opened pull request #8216: [qa] assert 'changePosition out of bounds' (master...Mf1606-qaFundrawtransaction) https://github.com/bitcoin/bitcoin/pull/8216
< GitHub193> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/66db2d62d598...ed2cd59e258f
< GitHub193> bitcoin/master facb6c0 MarcoFalke: [qa] mininode: fail on send_message instead of silent return
< GitHub193> bitcoin/master ed2cd59 MarcoFalke: Merge #8214: [qa] mininode: fail on send_message instead of silent return...
< GitHub104> [bitcoin] MarcoFalke closed pull request #8214: [qa] mininode: fail on send_message instead of silent return (master...Mf1606-qaMininodeAssert) https://github.com/bitcoin/bitcoin/pull/8214
< jonasschnelli> Hmm... just got: bitcoind: sync.cpp:125: void potential_deadlock_detected(const std::pair<void*, void*>&, const LockStack&, const LockStack&): Assertion `onlyMaybeDeadlock' failed.
< jonasschnelli> Aborted
< jonasschnelli> I though we have fixed this in master?
< sipa> jonasschnelli: not if there is an actual possible deadlocm
< jonasschnelli> https://0bin.net/paste/nMI2YWFnc1Fh-LoO#omlL+S3VWlMkDCWFmu48orx71gdeM-aXvU76fs0tQju
<@wumpus> that looks like a legit deadlock
<@wumpus> cs_vRecvMsg,cs_main,cs_filter,cs_vSend versus cs_vSend,cs_main, cs_inventory,cs_filter
<@wumpus> what version is that traceback from?
< sipa> MarcoFalke commented on the addednode refactor with that, maybe he has some indication that that's the cause? i'll investigate shortly
<@wumpus> ok, I was looking at the line numbers in master and ending up in really strange places in the code
< sipa> well, that refactor was merged
< MarcoFalke> Sry, I guess jonasschnelli was running 4286f43025149cf44207c3ad98e4a1f068520ada. Not current master
< jonasschnelli> MarcoFalke, sipa: I was running 37c98307ac7645412ac153e376e6e1020d867202
< jonasschnelli> and again. node stopped
< jonasschnelli> same lockorder
< jonasschnelli> I'll try again and if will update to master after next try
< luke-jr> cfields_: getting a 403 for OSX SDK in Travis again: https://travis-ci.org/bitcoinknots/bitcoin/jobs/138479709