Details
-
Story
-
Status: Closed
-
Medium
-
Resolution: Invalid
-
None
-
None
-
Unset
-
Unset
-
No
Description
The gossip unit tests should be improved in two aspects
Currently gossip unit tests fail around 2-3 times a day. Failures are intermittent and occur in a variety of tests.
Tests fail more often in the CI environment. This is probably due to the more constraint resources available in CI that lead to various timing effects the tests are vulnerable to.
Attachments
Issue Links
- relates to
-
FAB-12065 FAIL: TestLeaderYield failure of the gossip test
-
- Closed
-
-
FAB-13377 intermittent test failure in gossip TestDissemination
-
- Closed
-
-
FAB-13997 intermittent test failures in gossip/channel TestOnDemandGossip
-
- Closed
-
-
FAB-15688 gossip/comm tests doesn't end after 20 min
-
- Closed
-
-
FAB-12067 FAIL: TestEndedGoroutines gossip UT failure
-
- Closed
-
-
FAB-13539 Test flake fabric/gossip/comm.TestBasic
-
- Closed
-
-
FAB-13911 Integration test failure on "discover peer membership" spec
-
- Closed
-
-
FAB-14130 Flakey gossip tests - out of memory
-
- Closed
-
-
FAB-14936 Flaky unit test TestParallelSend
-
- Closed
-
-
FAB-14947 Intermittent test failure in TestNewGossipStateProvider_BatchingOfStateRequest
-
- Closed
-
-
FAB-14948 TestDifferentMessages Flake
-
- Closed
-
-
FAB-14956 UT flake - timeout due to deadlock in gossip/com/comm_test.go
-
- Closed
-
-
FAB-15032 FAIL github.com/hyperledger/fabric/gossip/service - panic after 20 minutes
-
- Closed
-
-
FAB-15093 TestGossipChannelEligibility not initialized mock
-
- Closed
-
-
FAB-13736 Intermittent test failure in gossip/gossip/algo/pull_test TestByzantineResponder
-
- Closed
-
-
FAB-13737 Intermittent test faiulre in gossip/identity/identity_test TestListInvalidIdentities
-
- Closed
-
-
FAB-13784 gossip/discovery - TestMsgStoreExpirationWithMembershipMessages
-
- Closed
-
-
FAB-14048 Unit test flake in TestDataLeakage
-
- To Do
-