For the exams skipped with “earlier releases not accessible”, it’s essential to have older variations of Bitcoin Core in an area listing. This listing has a folder for every model (named v25.0, v24.1, and so forth.). Inside every model’s folder is one other folder named bin, and inside which are the binaries for that model. The format of that can appear like:
|_ v25.0
|_ bin
|_ bitcoind
|_ bitcoin-cli
|_ bitcoin-tx
|_ bitcoin-wallet
|_ v24.1
|_ bin
|_ bitcoind
|_ bitcoin-cli
|_ bitcoin-tx
|_ bitcoin-wallet
|_ v23.0
|_ bin
|_ bitcoind
|_ bitcoin-cli
|_ bitcoin-tx
|_ bitcoin-wallet
...
This directoy should both be named releases in your present working listing, or you may present the complete path to it because the surroundings variable PREVIOUS_RELEASES_DIR
For the exams that require 1.1.1.1 and/or 2.2.2.2, it’s essential to create one other community interface in your machine and set their IP’s to 1.1.1.1 and a couple of.2.2.2. There are directions for doing this within the exams themselves.
From feature_bind_port_discover.py:
# We have to bind to a routable tackle for this take a look at to train the related code
# and likewise will need to have one other routable tackle on one other interface which should not
# be named "lo" or "lo0".
# To set these routable addresses on the machine, use:
# Linux:
# ifconfig lo:0 1.1.1.1/32 up && ifconfig lo:1 2.2.2.2/32 up # to arrange
# ifconfig lo:0 down && ifconfig lo:1 down # to take away it, after the take a look at
# FreeBSD:
# ifconfig em0 1.1.1.1/32 alias && ifconfig wlan0 2.2.2.2/32 alias # to arrange
# ifconfig em0 1.1.1.1 -alias && ifconfig wlan0 2.2.2.2 -alias # to take away it, after the take a look at
Then you may cross the --ihave1111and2222 and --ihave1111 choices to the exams.
