Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

calling_sync_routing_table is flaky #3875

Open
@tnull

Description

Just saw this in CI over at #3861:

---- routing::gossip::tests::calling_sync_routing_table stdout ----
thread 'routing::gossip::tests::calling_sync_routing_table' panicked at 'assertion failed: (msg.first_timestamp as u64) >= expected_timestamp - 60 * 60 * 24 * 7 * 2', lightning/src/routing/gossip.rs:3835:21
stack backtrace:
 0: rust_begin_unwind
 at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:584:5
 1: core::panicking::panic_fmt
 at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:142:14
 2: core::panicking::panic
 at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:48:5
 3: lightning::routing::gossip::tests::calling_sync_routing_table
 at ./src/routing/gossip.rs:3835:6
 4: lightning::routing::gossip::tests::calling_sync_routing_table::{{closure}}
 at ./src/routing/gossip.rs:3796:2
 5: core::ops::function::FnOnce::call_once
 at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/ops/function.rs:248:5
 6: core::ops::function::FnOnce::call_once
 at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failures:
 routing::gossip::tests::calling_sync_routing_table

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /