ci: Set TEST_RUNNER_PORT_MIN in test-each after cirrus runner switch#34687
ci: Set TEST_RUNNER_PORT_MIN in test-each after cirrus runner switch#34687fanquake merged 2 commits intobitcoin:masterfrom
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please copy-paste |
| needs: runners | ||
| runs-on: ${{ needs.runners.outputs.provider == 'cirrus' && 'ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-md' || 'ubuntu-24.04' }} | ||
| env: | ||
| TEST_RUNNER_PORT_MIN: "14000" # Use a larger port, to avoid colliding with CIRRUS_CACHE_HOST port 12321. |
There was a problem hiding this comment.
Changing CIRRUS_CACHE_HOST to be below 11000 would be a smaller diff in this file... wait - cirruslabs/cirrus-ci-docs#310 I guess we've been down that lane before.
For reference:
bitcoin/.github/workflows/ci.yml
Line 22 in 286de1e
bitcoin/test/functional/test_framework/util.py
Lines 468 to 471 in 286de1e
There was a problem hiding this comment.
note that cirrus-ci.com is different from cirrus-runners.app. I am not even sure if the runners have any docs on this
| needs: runners | ||
| runs-on: ${{ needs.runners.outputs.provider == 'cirrus' && 'ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-md' || 'ubuntu-24.04' }} | ||
| env: | ||
| TEST_RUNNER_PORT_MIN: "14000" # Use a larger port, to avoid colliding with CIRRUS_CACHE_HOST port 12321. |
There was a problem hiding this comment.
Changing CIRRUS_CACHE_HOST to be below 11000 would be a smaller diff in this file... wait - cirruslabs/cirrus-ci-docs#310 I guess we've been down that lane before.
For reference:
bitcoin/.github/workflows/ci.yml
Line 22 in 286de1e
bitcoin/test/functional/test_framework/util.py
Lines 468 to 471 in 286de1e
This is needed after the recent switch to cirrus runners in the task in commit c8c9c1e.
Otherwise, the CI will fail:
(https://github.com/bitcoin/bitcoin/actions/runs/22398358349/job/64837827234?pr=31723#step:9:2605)
Also, include a random second commit, so that the CI task is run in this pull.