`test_cln` is flaky now

[tnull]

After #524 we now started seeing test_cln failing with the following message, which is curious, as it seems to be working as expected locally:

thread 'test_cln' panicked at tests/integration_tests_cln.rs:89:23:
node got unexpected event!: ChannelClosed { channel_id: d7011b89329aa3686e46769cedede561a406fd764419b8ba02cbbdb9d6b89eb9, user_channel_id: UserChannelId(218640611731153854047642377166051042969), counterparty_node_id: Some(PublicKey(29975387f8f71e43d7355942980f73450be266cc424d3adca4fc840b72d176440f36b19f80245464c148c4545065cfd16c5130c8ded025a8c05267374e0ca6c4)), reason: Some(DisconnectedPeer) }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    test_cln

[Camillarhi]

Hi @tnull,

I wanted to note that this issue is also affecting my PR (#519). I ran the tests locally using the same Docker Compose setup (docker-compose-cln.yml) and they passed successfully, which suggests the problem might be specific to the CI environment.

If there’s anything I can do to help debug this further, let me know!

[Camillarhi]

Hi @tnull,

I wanted to note that this issue is also affecting my PR (#519). I ran the tests locally using the same Docker Compose setup (docker-compose-cln.yml) and they passed successfully, which suggests the problem might be specific to the CI environment.

If there’s anything I can do to help debug this further, let me know!

Hi @tnull ,

I rebased my branch onto the latest dev (including changes from #524), and now test_cln passes both locally and in CI. This suggests the issue was likely caused by an outdated branch state.

It seems resolved for now, but let me know if anything else needs to be checked!