-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: js-waku interoperability tests are failing since v0.33.1 #3219
Labels
bug
Something isn't working
Comments
Checking CI runtimes for nwaku - js-waku
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.:
npm install
npm run build
WAKUNODE_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.
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
The text was updated successfully, but these errors were encountered: