tomaka
commented
5 months ago CI logs expire
Closed ryanleecode closed 5 months ago
tomaka
commented
5 months ago CI logs expire
tomaka
commented
5 months ago Looks like the runtime service gets stuck after line 516
EDIT: actually, it doesn't really seem to do much more in the non-stuck logs.
tomaka
commented
5 months ago Interestingly, the tx service doesn't receive updates about the chain in the stuck logs (and does in the non-stuck logs), so it's probably related to the sync service.
EDIT: for reference this comment was wrong, as the tx service subscribes to the runtime service and not to the sync service
tomaka
commented
5 months ago The trace logs would be extremely useful in this case.
ryanleecode
When connecting to kusama it randomly gets stuck on the block in chainspec. But this isn't consistent behaviour between runs
smoldot: 2.0.28
chainspec: https://gist.github.com/ryanleecode/17aeb2a15d2c9137b20dd02a6bcfbbbe
Repro: https://stackblitz.com/~/github.com/ryanleecode/kusama-test
Stuck Logs: https://github.com/ryanleecode/kusama-test/actions/runs/9529257265/job/26267801534#step:7:382
Not Stuck Logs: https://github.com/ryanleecode/kusama-test/actions/runs/9529290166/job/26267875999#step:7:518