status-go
status-go copied to clipboard
status-im
Flaky test - TestBasicWakuV2
0x3af229605178b48da99111097234feeb7b4e08c96ec50cfbe339ad862a6839bd", "receivedTime": 1696507482315651441, "payloadSizeBytes": 796}
2023-10-05T12:04:42.315Z DEBUG wakuv2/waku.go:1337 cached w envelope {"envelopeHash": "0x3af229605178b48da99111097234feeb7b4e08c96ec50cfbe339ad862a6839bd"}
2023-10-05T12:04:42.315Z DEBUG wakuv2/waku.go:1369 filters did not match {"hash": "0x3af229605178b48da99111097234feeb7b4e08c96ec50cfbe339ad862a6839bd", "contentTopic": "/waku/1/0xfa61c2f2/rfc26"}
waku_test.go:162:
Error Trace: /home/jenkins/workspace/status-go_prs_tests_PR-4070/wakuv2/waku_test.go:162
Error: Should not be zero, but was 0
Test: TestBasicWakuV2
It's back again: TestBasicWakuV2: 80.0% (16 of 20 failed)
cc @chaitanyaprem
It's back again:
TestBasicWakuV2: 80.0% (16 of 20 failed)cc @chaitanyaprem
looks like staging fleet connectivity is having some issues due to https://github.com/status-im/infra-shards/issues/33 which is causing test to fail randomly.
looks like staging fleet connectivity is having some issues due to https://github.com/status-im/infra-shards/issues/33 which is causing test to fail randomly.
Hmmm, maybe we should consider re-writing tests, so that they don't use real network? Either mock it, or launch a fleet on the same machine for tests.
cc @chaitanyaprem
looks like staging fleet connectivity is having some issues due to status-im/infra-shards#33 which is causing test to fail randomly.
Hmmm, maybe we should consider re-writing tests, so that they don't use real network? Either mock it, or launch a fleet on the same machine for tests.
cc @chaitanyaprem
Yep, but mocking might not be useful as we want to test waku(which involves connecting to fleet nodes atleast). Will review the reason why these tests are written and see if we can change them.
thoughts @richard-ramos ?
From time to time it is blocking the PRs now.
https://ci.status.im/job/status-go/job/prs/job/tests/job/PR-6569/6/artifact/report_rerun_fails_0.txt
github.com/status-im/status-go/wakuv2.TestBasicWakuV2: 3 runs, 3 failures
https://ci.status.im/job/status-go/job/prs/job/tests/job/PR-6569/6/artifact/test_0.log
=== Failed
=== FAIL: wakuv2 TestBasicWakuV2 (0.00s)
waku_test.go:180:
Error Trace: /home/jenkins/workspace/status-go_prs_tests_PR-6569/wakuv2/waku_test.go:180
Error: Received unexpected error:
Get "http://localhost:9647/debug/v1/info": dial tcp 127.0.0.1:9647: connect: connection refused
Test: TestBasicWakuV2
=== FAIL: wakuv2 TestBasicWakuV2 (re-run 1) (0.00s)
waku_test.go:180:
Error Trace: /home/jenkins/workspace/status-go_prs_tests_PR-6569/wakuv2/waku_test.go:180
Error: Received unexpected error:
Get "http://localhost:9647/debug/v1/info": dial tcp 127.0.0.1:9647: connect: connection refused
Test: TestBasicWakuV2
=== FAIL: wakuv2 TestBasicWakuV2 (re-run 2) (0.00s)
waku_test.go:180:
Error Trace: /home/jenkins/workspace/status-go_prs_tests_PR-6569/wakuv2/waku_test.go:180
Error: Received unexpected error:
Get "http://localhost:9647/debug/v1/info": dial tcp 127.0.0.1:9647: connect: connection refused
Test: TestBasicWakuV2
DONE 3 runs, 1871 tests, 24 skipped, 3 failures in 248.355s
It seems to be happening after: https://github.com/status-im/status-go/pull/6408
