core-lightning/gossipd/gossip_wire.csv
Rusty Russell 147eaced2e developer: consolidiate gossip timing options into one --dev-fast-gossip.
It's generally clearer to have simple hardcoded numbers with an
#if DEVELOPER around it, than apparent variables which aren't, really.

Interestingly, our pruning test was always kinda broken: we have to pass
two cycles, since l2 will refresh the channel once to avoid pruning.

Do the more obvious thing, and cut the network in half and check that
l1 and l3 time out.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-20 06:55:00 +00:00

6.2 KiB

1#include <common/cryptomsg.h>
2#include <common/wireaddr.h>
3#include <wire/gen_onion_wire.h>
4# Initialize the gossip daemon.
5# Pass JSON-RPC getnodes call through
6#include <lightningd/gossip_msg.h>
7# Pass JSON-RPC getroute call through
8# Ping/pong test. Waits for a reply if it expects one.
9# False if id in gossip_ping was unknown.
10# 0 == no pong expected
11# Test of query_short_channel_ids. Master->gossipd
12# Gossipd -> master
13# Test gossip timestamp filtering.
14# Test of query_channel_range. Master->gossipd
15# Gossipd -> master
16# Set artificial maximum reply_channel_range size. Master->gossipd
17# gossipd->master: we're closing this channel.
18# Gossipd->master get this tx output please.
19# master->gossipd an htlc failed with this onion error.
20# master -> gossipd: stop gossip timers.
21# master -> gossipd: do you have a memleak?
22# master -> gossipd: please rewrite the gossip_store
23# gossipd -> master: ok
24#include <common/bolt11.h>
25# master -> gossipd: get route_info for our incoming channels
26# gossipd -> master: here they are.