bitcoin

History

MarcoFalke 4c4ff4911a Merge #16961 : test: Remove python dead code linter `f4beb4996d` test: Remove python dead code linter (Wladimir J. van der Laan) Pull request description: Primarily I'd like to remove this because it is very imprecise, due to Python's dynamic nature, giving it a large list of false positives that need to be listed as exceptions. See for example #16906. It's also a frequent source of complaints. I'm doubtful of the usefulness of checking for dead code in a linter in the first place. Having some dead code in the test framework for a while is not a disaster. ACKs for top commit: sdaftuar: utACK `f4beb4996d` practicalswift: ACK `f4beb4996d` -- diff looks correct jamesob: ACK `f4beb4996d` Tree-SHA512: 329b1555210311d5d15799fd2cb794b3208b0ac4d8a2ffaf4dece1bcc3e0e8b1fe952d5e7a394f94a98919cab579fb579eae7db2a796cc9a1a42ef495dd17507		5 years ago
..
extended_lint	ci: Rename .travis/ to ./ci/	5 years ago
lint	test: Remove python dead code linter	5 years ago
retry	ci: Remove dependence on travis, use it as fallback env	5 years ago
test	ci: Remove TRAVIS env vars	5 years ago
README.md	ci: Add environment files for all settings	5 years ago
test_run_all.sh	ci: Add environment files for all settings	5 years ago

README.md

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

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 ccache bash git

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

Be aware that the tests will be build 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.