e35aeddf4a
## Issue being fixed or feature implemented During reviewing TODO were found some TODOes that can be done now. ## What was done? - fix: follow-up dash#3467 - replaced commented code to disabled code - follow-up bitcoin#16394 - uncommented code related to `watchonly` feature - removed out-dated TODO in `rpc/masternode.cpp` (already done) - fix: renamed name of clean up test_unittests: removed TODO and updated name of variable TRAVIS - rewritten todo inside `.travis.yml` - fix: adds a missing description for result of rpc `mnsync` Last commit (`mnsync`) is an only candidate for backport to v19, other changes are non significant. ## How Has This Been Tested? Run functional/unit tests ## Breaking Changes No breaking changes ## Checklist: - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone |
||
|---|---|---|
| .. | ||
| dash | ||
| extended_lint | ||
| lint | ||
| retry | ||
| test | ||
| README.md | ||
| test_run_all.sh | ||
ci scripts
This directory contains scripts for each build step in each build stage.
Currently three stages lint, extended_lint and test are defined. Each stage has its own lifecycle, similar to the
Travis CI lifecycle. Every script in here is named
and numbered according to which stage and lifecycle step it belongs to.
Running a stage locally
Be aware that the tests will be built and run in-place, so please run at your own risk. If the repository is not a fresh git clone, you might have to clean files from previous builds or test runs first.
The ci needs to perform various sysadmin tasks such as installing packages or writing to the user's home directory. While most of the actions are done inside a docker container, this is not possible for all. Thus, cache directories, such as the depends cache or ccache, are mounted as read-write into the docker container. While it should be fine to run the ci system locally on you development box, the ci scripts can generally be assumed to have received less review and testing compared to other parts of the codebase. If you want to keep the work tree clean, you might want to run the ci system in a virtual machine with a Linux operating system of your choice.
To allow for a wide range of tested environments, but also ensure reproducibility to some extent, the test stage
requires docker to be installed. To install all requirements on Ubuntu, run
sudo apt install docker.io bash
To run the default test stage,
./ci/test_run_all.sh
To run the test stage with a specific configuration,
FILE_ENV="./ci/test/00_setup_env_arm.sh" ./ci/test_run_all.sh