fix: fix flaky calling_sync_routing_table by capturing timestamp earlier #4399
+4
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes flakiness in the
calling_sync_routing_tabletest inlightning/src/routing/gossip.rsunder CI load by capturingexpected_timestampbefore callingpeer_connected(). Previously, the test captured the timestamp after the call, so under load any elapsed time could cause assertions comparingmsg.first_timestampagainstexpected_timestampto fail. Moving the capture earlier ensuresexpected_timestamp <= msg.first_timestamp, making the assertions deterministic while leaving test logic unchanged. This change addresses intermittent CI failures without affecting functionality.Closes: #3875