bug: js-waku interoperability tests are failing since v0.33.1 #3219
Description
Problem
Since a noticable time we see nwaku CI's js-waku tests turned red constantly.
Impact
This is a major issue if we are not able to clearly validate the interoperability with js-waku and point out regressions during PR and release validation.
To reproduce
Option a.: check nwaku PRs CI results
Option b.:
- checkout js-waku
npm installnpm run buildWAKUNODE_IMAGE=harbor.status.im/wakuorg/nwaku:<?release-you-want-to-test??> npm run test:node
Findings
In nwaku CI tests we clearly see a point where js-waku tests are gone incredibly long - instead oh ~half an hour it lasts 1 to 5-6h.
All the logs shows connection issues to the nwaku node - that runs as dockerized for the tests. After a while js-waku test just keep trying to connect forever to an unreachable node.
On local machine it happens quite similar, but test crashes with running out of node-js heap.
- @Ivansete-status found that PR chore: lightpush better feedback if lightpush service node without peers #2951 might introduced a breaking change that has not been perfectly covered in js-waku sdk-0.28
Expected behavior
js-waku tests shall be all ok and green on CI.
Screenshots/logs
nwaku version/commit hash
It is hard to point out exact combination of js-waku and nwaku versions and commits that made the tests fail.
We know that js-waku 08fc2d133 against nwaku v0.31.0 just make it.
cc: @Ivansete-status
Metadata
Metadata
Assignees
Labels
Type
Projects
Status