Browse Source
Usually Travis triggers corner cases because it's so slow, but this time the moons aligned, and it managed to fail test_node_reannounce because it generated the updated node_announcement with the same timestamp as the old one. This is because we only updated "last_announce_timestamp" when we generated the announcement, not when we got it off the wire or loaded it from the gossip store. The fix is to ask the routing code what the latest timestamp is; we could still generate a clashing timestamp if (1) the gossip store is lost, and (2) we restart within one second. Hard to care. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>fee-tracking2
Rusty Russell
6 years ago
1 changed files with 9 additions and 7 deletions
Loading…
Reference in new issue