< fanquake>
Probably just broke the record for time from PR opened to rebased required.
< fanquake>
< 2 minutes :p
< wumpus>
lol if only ariard had waited a few minutes
< wumpus>
(or, had I managed to merge it sooner, I had github-merged it twice before and run the usual test-steps but there was a merge in between every time :-) )
< luke-jr>
wumpus: of course, it's the branch time that matters, not the PR open time
< dongcarl>
However, looking at call sites of `SetNameProxy` there's only one and it sets it to be the same as all other nets
< bitcoin-git>
[bitcoin] jnewbery closed pull request #15778: [wallet] Move maxtxfee from node to wallet (master...remove_maxtxfeerate_from_node) https://github.com/bitcoin/bitcoin/pull/15778
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #15788: test: Unify testing setups for fuzz, bench, and unit tests (master...1904-testUnify) https://github.com/bitcoin/bitcoin/pull/15788
< bitcoin-git>
[bitcoin] jnewbery reopened pull request #15778: [wallet] Move maxtxfee from node to wallet (master...remove_maxtxfeerate_from_node) https://github.com/bitcoin/bitcoin/pull/15778
< jnewbery>
Are people seeing more Travis timeouts that before on their PRs?
< jnewbery>
Error! Initial build successful, but not enough time remains to run later build stages and tests. Please manually re-run this job by using the travis restart button or asking a bitcoin maintainer to restart. The next run should not time out because the build cache has been saved.
< jnewbery>
*more than before
< jnewbery>
Seems to happen on most of my PRs these days