ElementsProject / ElementsProject/lightning
CI Flake `test_funding_cancel_race`
- Vorherrschende Sprache
- C
- Sterne
- 3.1k
- Forks
- 1k
- Ø Merge
- 3 T. 13 Std.
- Gemergte PRs (30 T.)
- 23
Beschreibung
Server delay from receiving WIRE_OPEN_CHANNEL, activating `connectd` takes 11068msec which triggers `BROKEN` message for taking too long.
([CI Log](https://github.com/ElementsProject/lightning/actions/runs/28464251949/job/84363043473))
Relevant portion of log:
```
lightningd-6 2026-06-30T18:07:40.211Z DEBUG 038194b5f32bdf0aa59812c86c4ef7ad2f294104fa027d1ace9b469bb6f88cf37b-connectd: Activating for message WIRE_OPEN_CHANNEL
lightningd-20 2026-06-30T18:07:40.925Z DEBUG gossipd: seeker: no peers, waiting
lightningd-18 2026-06-30T18:07:41.387Z DEBUG gossipd: seeker: no peers, waiting
lightningd-21 2026-06-30T18:07:41.668Z DEBUG gossipd: seeker: no peers, waiting
lightningd-8 2026-06-30T18:07:41.961Z DEBUG gossipd: seeker: no peers, waiting
lightningd-17 2026-06-30T18:07:41.978Z DEBUG gossipd: seeker: no peers, waiting
lightningd-15 2026-06-30T18:07:42.137Z DEBUG gossipd: seeker: no peers, waiting
lightningd-13 2026-06-30T18:07:42.294Z DEBUG gossipd: seeker: no peers, waiting
lightningd-14 2026-06-30T18:07:42.479Z DEBUG gossipd: seeker: no peers, waiting
lightningd-16 2026-06-30T18:07:42.695Z DEBUG gossipd: seeker: no peers, waiting
lightningd-19 2026-06-30T18:07:42.723Z DEBUG gossipd: seeker: no peers, waiting
lightningd-7 2026-06-30T18:07:42.940Z DEBUG gossipd: seeker: no peers, waiting
lightningd-11 2026-06-30T18:07:43.173Z DEBUG gossipd: seeker: no peers, waiting
lightningd-9 2026-06-30T18:07:43.484Z DEBUG gossipd: seeker: no peers, waiting
lightningd-10 2026-06-30T18:07:43.523Z DEBUG gossipd: seeker: no peers, waiting
lightningd-12 2026-06-30T18:07:43.988Z DEBUG gossipd: seeker: no peers, waiting
lightningd-20 2026-06-30T18:07:45.926Z DEBUG gossipd: seeker: no peers, waiting
lightningd-18 2026-06-30T18:07:46.388Z DEBUG gossipd: seeker: no peers, waiting
lightningd-21 2026-06-30T18:07:46.722Z DEBUG gossipd: seeker: no peers, waiting
lightningd-17 2026-06-30T18:07:46.982Z DEBUG gossipd: seeker: no peers, waiting
lightningd-8 2026-06-30T18:07:47.032Z DEBUG gossipd: seeker: no peers, waiting
lightningd-15 2026-06-30T18:07:47.276Z DEBUG gossipd: seeker: no peers, waiting
lightningd-13 2026-06-30T18:07:47.294Z DEBUG gossipd: seeker: no peers, waiting
lightningd-14 2026-06-30T18:07:47.690Z DEBUG gossipd: seeker: no peers, waiting
lightningd-16 2026-06-30T18:07:47.738Z DEBUG gossipd: seeker: no peers, waiting
lightningd-19 2026-06-30T18:07:47.740Z DEBUG gossipd: seeker: no peers, waiting
lightningd-7 2026-06-30T18:07:47.825Z DEBUG gossipd: seeker: no peers, waiting
lightningd-11 2026-06-30T18:07:48.178Z DEBUG gossipd: seeker: no peers, waiting
lightningd-9 2026-06-30T18:07:48.526Z DEBUG gossipd: seeker: no peers, waiting
lightningd-10 2026-06-30T18:07:48.573Z DEBUG gossipd: seeker: no peers, waiting
lightningd-12 2026-06-30T18:07:49.076Z DEBUG gossipd: seeker: no peers, waiting
lightningd-6 2026-06-30T18:07:50.978Z DEBUG 038194b5f32bdf0aa59812c86c4ef7ad2f294104fa027d1ace9b469bb6f88cf37b-openingd-chan#1: pid 49751, msgfd 91
lightningd-20 2026-06-30T18:07:51.170Z DEBUG gossipd: seeker: no peers, waiting
lightningd-6 2026-06-30T18:07:51.225Z DEBUG hsmd: Client: Received message 30 from client
lightningd-6 2026-06-30T18:07:51.277Z DEBUG hsmd: Client: Received message 10 from client
lightningd-6 2026-06-30T18:07:51.278Z DEBUG hsmd: new_client: 1
lightningd-6 2026-06-30T18:07:51.278Z **BROKEN** 038194b5f32bdf0aa59812c86c4ef7ad2f294104fa027d1ace9b469bb6f88cf37b-connectd: wake delay for WIRE_OPEN_CHANNEL: 11068msec
```
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Das Issue benennt test_funding_cancel_race und enthält ein CI-Log, das die Aktivierung von WIRE_OPEN_CHANNEL in connectd zusammen mit Aktivitäten von gossipd zeigt. Führe zunächst diesen Test aus und vergleiche seine Ausgabe mit dem verlinkten CI-Log; verfolge die Aufweckverzögerung und überprüfe, dass die Race Condition in CI nicht mehr sporadisch fehlschlägt oder eine BROKEN-Meldung ausgibt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- c, github-actions
- Bereich
- ci-cd, networking, testing
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 38/100