Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pytest: fix flaky 'Bad gossip' errors #3228

Merged

Conversation

rustyrussell
Copy link
Contributor

@rustyrussell rustyrussell commented Oct 31, 2019

One real test fix, and a rework of our slightly-broken "push this msg through despite timestamp_filter" option which was causing many more "Bad gossip" order messages.

@rustyrussell rustyrussell added this to the 0.7.4 milestone Oct 31, 2019
@rustyrussell rustyrussell requested a review from cdecker October 31, 2019 04:17
@rustyrussell rustyrussell changed the title pytest: fix flaky 'Bad gossip' error in test_block_backfill WIP: pytest: fix flaky 'Bad gossip' errors Nov 1, 2019
@cdecker cdecker changed the title WIP: pytest: fix flaky 'Bad gossip' errors pytest: fix flaky 'Bad gossip' errors Nov 1, 2019
@rustyrussell rustyrussell force-pushed the test_block_backfill-deflake branch 2 times, most recently from 2113e1d to e21ea85 Compare November 4, 2019 00:38
@rustyrussell rustyrussell force-pushed the test_block_backfill-deflake branch from e21ea85 to 6a8085c Compare November 4, 2019 02:04
Sometimes the l3 seeker asks for scids, and the reply contains the
channel which is then closed by the time it checks, so it considers
the updates bad gossip.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
We're about to change it so we always send our local messages, which
breaks this test.  Add a new node which doesn't have any local
messages, so the test works correctly.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This tells clients to ignore any timestamp_filter and always
send this message when it sees it.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This is a better fix than doing it manually, which turned out
to do it in the wrong order (node_announcement followed by
channel_announcement) anyway.

Should fix many "Bad gossip" messages.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
@rustyrussell rustyrussell force-pushed the test_block_backfill-deflake branch from 6a8085c to 0dcc5f3 Compare November 4, 2019 03:32
@rustyrussell rustyrussell mentioned this pull request Nov 4, 2019
@cdecker
Copy link
Member

cdecker commented Nov 4, 2019

The reduction in surface by passing in the push flag is a nice change, allows us to spread the logic out far less.

You're missing a Changelog entry in one of your commit messages, or opt-out using Changelog-None in one of the commit messages. The bot is currently set to pending rather than failure for that check, but it'd be nice to get used to adding those :-)

ACK 0dcc5f3

@cdecker cdecker merged commit 7f45e55 into ElementsProject:master Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants