ChainSafe / ChainSafe/gossamer

Fix flaky tests

Open
#1,975 3 comments 0 reactions 0 assignees View on GitHub
Epic
Dominant language
Go
Stars
454
Forks
144
PR merge metrics
No merged PRs in 30d

Description

Since some tests fail occasionally, it might be an indicator of bad logic which could cause memory leaks and/or data races. Related to #1936 and #1968

These should be investigated. The following tests were found to fail occasionally (feel free to remove/add):

- [x] #2158
- [ ] #2159
- [x] #2160
- [x] #2161
- [x] #2163
- [ ] #2162
- [x] #2164
- [x] #2165
- [x] ~#2166~ (moved to #2147)
- [x] #2167
- [x] #2168
- [x] #2280
- [ ] TestHandleTransactionMessage

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the remaining unchecked entries, #2159, #2162, and TestHandleTransactionMessage, alongside related issues #1936 and #1968. Investigate the intermittent failures and determine whether they indicate bad logic, memory leaks, or data races; done means the identified flaky tests are resolved or their status is clearly updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.