An automated test for checking that a PR can sync
- Dominant language
- C++
- Stars
- 2.5k
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
As part of the automated travis build (or maybe it could be a separate thing from travis) , we should try to run and sync the built lbrycrd on testnet to see if it can a) sync from scratch and b) start up when its already synced and can succesfuly recieve a couple of blocks.
Not sure if this is possible just using travis (might take too long? use too much disk space?). We might have to set up some servers for this.
Contributor guide
Research direction
Start by reviewing the automated Travis build and how the built lbrycrd is run against testnet. Define whether the check belongs in Travis or separate infrastructure, and consider the stated cases: syncing from scratch and restarting an already synced node that receives a couple of blocks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain, ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100