02:23 < gmaxwell> I think #9420 can obviously be merged.

02:23 < gribble> https://github.com/bitcoin/bitcoin/issues/9420 | Fix linker error when configured with --enable-lcov by droark · Pull Request #9420 · bitcoin/bitcoin · GitHub

07:44 < bitcoin-git> [bitcoin] jonasschnelli pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/dce853ef76ef...bebe3697fdad

07:44 < bitcoin-git> bitcoin/master e2b5c98 Douglas Roark: Fix linker error when configured with --enable-lcov

07:44 < bitcoin-git> bitcoin/master bebe369 Jonas Schnelli: Merge #9420: Fix linker error when configured with --enable-lcov...

07:44 < bitcoin-git> [bitcoin] jonasschnelli closed pull request #9420: Fix linker error when configured with --enable-lcov (master...fixlcov) https://github.com/bitcoin/bitcoin/pull/9420

08:48 < jonasschnelli> Right? Finding the active headers tip with (only) getchaintips is not possible right now?

08:48 < jonasschnelli> Assume we have a split and two headers-only chains (with the same height), you can't see which headers chain has more work?

09:41 < bitcoin-git> [bitcoin] jonasschnelli opened pull request #9446: SetMerkleBranch: remove unused code, remove cs_main lock requirement (master...2016/12/merklebranch) https://github.com/bitcoin/bitcoin/pull/9446

15:35 < bitcoin-git> [bitcoin] morcos opened pull request #9447: Allow 2 simultaneous block downloads (master...doubledownload) https://github.com/bitcoin/bitcoin/pull/9447

15:49 < bitcoin-git> [bitcoin] MarcoFalke reopened pull request #7522: Bugfix: Only use git for build info if the repository is actually the right one (master...bugfix_gitdir) https://github.com/bitcoin/bitcoin/pull/7522

23:51 < morcos> BlueMatt: The issue of a block request coming in before you've updated the tip is what's causing the Travis failure in 9447, it's not clear to me why it happens reliably there and not in 9375 as it seems like it should in 9375

23:52 < morcos> in the sendheaders.py test, you announce a reorg and then FindNextBlocksToDownload kicks in when you've announced enough blocks on the new chain to match nChainWork of your tip

23:53 < morcos> it turns out that the block requests generated by FindNextBlocksToDownload can actually arrive before tip is updated in the peer announcing the reorg.. it might be as simple as checking the cached block in ProcessGetData as well..