mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-12-29 10:04:41 +01:00
Code Issues Projects Releases Wiki Activity
558abe288a
core-lightning/.github/workflows/ci.yaml

243 lines
8.0 KiB
YAML
Raw Normal View History

gci: Add basic configuration for Github Actions as CI
2021-01-09 16:23:06 +01:00
---
name: Continuous Integration
on: [push, pull_request]
jobs:
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
smoke-test:
name: Smoke Test Config ${{ matrix.cfg }}
runs-on: ubuntu-20.04
gci: Expand matrix to include all CI configurations
2021-01-13 11:21:57 +01:00
env:
DEVELOPER: 1
VALGRIND: 0
EXPERIMENTAL_FEATURES: 0
COMPAT: 1
gci: Add basic configuration for Github Actions as CI
2021-01-09 16:23:06 +01:00
strategy:
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
fail-fast: true
gci: Expand matrix to include all CI configurations
2021-01-13 11:21:57 +01:00
matrix:
include:
gci: Give each configuration an CFG value to identify them later We don't have a good way of referring to the configuration that failed, so let's give them a numberic ID. Particularly useful for the artifacts that'd be overwritten otherwise.
2021-01-23 11:55:52 +01:00
# CFG us just an enumeration so we can refer to the configurations more easily
gci: Disable test for NO_PYTHON It's been causing me quite some headache, and I don't see the point in jumping through the hoops for something that can be trivially fixed by having the required build tools.
2021-03-08 13:55:14 +01:00
- {CFG: 1, TEST_CMD: "make"}
make: Add target to check generated/derived files were checked in A new target `check-gen-updated` to verify that all derived/generated files that were modified were also checked in. This is used on CI to check, and is not added to `check` since it'll complain on dirty trees, i.e., before the devs check in their changes. Suggested-by: Rusty Russell <@rustyrussell>
2021-02-10 11:23:34 +01:00
- {CFG: 2, TEST_CMD: "make check-source check-units installcheck check-gen-updated", COPTFLAGS: "-O3"}
gci: Give each configuration an CFG value to identify them later We don't have a good way of referring to the configuration that failed, so let's give them a numberic ID. Particularly useful for the artifacts that'd be overwritten otherwise.
2021-01-23 11:55:52 +01:00
- {CFG: 3, ARCH: 32, TEST_CMD: "make check-source check-units installcheck", DEVELOPER: 0}
make: Add target to check generated/derived files were checked in A new target `check-gen-updated` to verify that all derived/generated files that were modified were also checked in. This is used on CI to check, and is not added to `check` since it'll complain on dirty trees, i.e., before the devs check in their changes. Suggested-by: Rusty Russell <@rustyrussell>
2021-02-10 11:23:34 +01:00
- {CFG: 4, TEST_CMD: "make check-source check-units installcheck check-gen-updated", EXPERIMENTAL_FEATURES: 1}
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
steps:
- name: Checkout
uses: actions/checkout@v2.0.0
- name: Set up Python 3.6
uses: actions/setup-python@v2
with:
python-version: 3.6
gci: Expand matrix to include all CI configurations
2021-01-13 11:21:57 +01:00
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
- name: Install dependencies
run: |
bash -x .github/scripts/setup.sh
- name: Build
env:
VALGRIND: ${{ matrix.VALGRIND }}
DEVELOPER: ${{ matrix.DEVELOPER }}
EXPERIMENTAL_FEATURES: ${{ matrix.EXPERIMENTAL_FEATURES }}
COMPILER: ${{ matrix.COMPILER }}
ARCH: ${{ matrix.ARCH }}
COMPAT: ${{ matrix.COMPAT }}
PYTEST_PAR: ${{ matrix.PYTEST_PAR }}
PYTEST_OPTS: ${{ matrix.PYTEST_OPTS }}
NO_PYTHON: ${{ matrix.NO_PYTHON }}
COPTFLAGS: ${{ matrix.COPTFLAGS }}
NETWORK: ${{ matrix.NETWORK }}
TEST_CMD: ${{ matrix.TEST_CMD }}
TEST_GROUP_COUNT: ${{ matrix.TEST_GROUP_COUNT }}
TEST_GROUP: ${{ matrix.TEST_GROUP }}
run: |
bash -x .github/scripts/build.sh
- name: Upload Unit Test Results
if: always()
uses: actions/upload-artifact@v2
with:
name: Junit Report ${{ github.run_number }}.${{ matrix.cfg }}
path: report.*
if-no-files-found: ignore
ci: turn on proto-tests for the CI builds Add an extra run configuration for the proto-tests. Proto-tests require DEVELOPER=1; enabling EXPERIMENTAL_FEATURES=1 by default ensures that experimental additions are automatically put under test also.
2021-03-19 17:52:39 +01:00
proto-test:
name: Protocol Test Config
runs-on: ubuntu-20.04
needs: [smoke-test]
env:
DEVELOPER: 1
EXPERIMENTAL_FEATURES: 1
COMPAT: 0
PYTEST_PAR: 2
TEST_CMD: "make check-protos"
TEST_GROUP: 1
TEST_GROUP_COUNT: 1
strategy:
fail-fast: true
matrix:
compiler: [gcc]
db: [postgres, sqlite3]
valgrind: [0, 1]
network: [regtest] # FIXME: add liquid-regtest
include:
- {compiler: clang, db: sqlite3, valgrind: 1}
- {compiler: clang, db: postgres, valgrind: 1}
- {arch: arm32v7, TARGET_HOST: arm-linux-gnueabihf, valgrind: 1, network: regtest}
- {arch: arm64v8, TARGET_HOST: aarch64-linux-gnu, valgrind: 1, network: regtest}
steps:
- name: Checkout
uses: actions/checkout@v2.0.0
- name: Setup Python 3.6
uses: actions/setup-python@v2
with:
python-version: 3.6
- name: Install dependencies
run: |
bash -x .github/scripts/setup.sh
- name: Build
env:
ARCH: ${{ matrix.arch }}
COMPILER: ${{ matrix.compiler }}
DB: ${{ matrix.db }}
NETWORK: ${{ matrix.network }}
TARGET_HOST: ${{ matrix.TARGET_HOST }}
VALGRIND: ${{ matrix.valgrind }}
run: |
bash -x .github/scripts/build.sh
- name: Upload Unit Test Results
if: always()
uses: actions/upload-artifact@v2
with:
name: Junit Report ${{ github.run_number }}.{{ matrix.cfg }}
path: report.*
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
normal-test:
name: Normal Test Config ${{ matrix.cfg }}
runs-on: ubuntu-20.04
needs: [smoke-test]
env:
DEVELOPER: 1
VALGRIND: 0
EXPERIMENTAL_FEATURES: 0
COMPAT: 1
strategy:
fail-fast: false
matrix:
include:
gci: Expand matrix to include all CI configurations
2021-01-13 11:21:57 +01:00
# All of the following will just run `make pytest`
CI: make sure we do a fuzzing build. Suggested-by: Christian Reitter. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-04-19 05:56:09 +02:00
- {CFG: 5, COMPILER: clang, FUZZING: 1}
gci: Give each configuration an CFG value to identify them later We don't have a good way of referring to the configuration that failed, so let's give them a numberic ID. Particularly useful for the artifacts that'd be overwritten otherwise.
2021-01-23 11:55:52 +01:00
- {CFG: 6, COMPILER: gcc, TEST_CHECK_DBSTMTS: 1}
- {CFG: 7, DEVELOPER: 0, COMPAT: 0, TEST_GROUP: 1, TEST_GROUP_COUNT: 2}
- {CFG: 8, DEVELOPER: 0, COMPAT: 0, TEST_GROUP: 2, TEST_GROUP_COUNT: 2}
gci: Expand matrix to include all CI configurations
2021-01-13 11:21:57 +01:00
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
# Various other configurations
- {CFG: 19, NETWORK: liquid-regtest}
- {CFG: 20, DB: postgres, PYTEST_PAR: 2}
# The cross-compiled versions
- {CFG: 21, ARCH: arm32v7, TARGET_HOST: arm-linux-gnueabihf}
- {CFG: 22, ARCH: arm64v8, TARGET_HOST: aarch64-linux-gnu}
CI: Disable EXPERIMENTAL_FEATURES temporarily. It's flaky, and interfering with the rc1 release. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-03-18 04:29:37 +01:00
# Disabled for 0.10.0-rc1
# - {CFG: 23, EXPERIMENTAL_FEATURES: 1}
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
steps:
- name: Checkout
uses: actions/checkout@v2.0.0
- name: Set up Python 3.6
uses: actions/setup-python@v2
with:
python-version: 3.6
- name: Install dependencies
run: |
bash -x .github/scripts/setup.sh
- name: Build
env:
VALGRIND: ${{ matrix.VALGRIND }}
DEVELOPER: ${{ matrix.DEVELOPER }}
EXPERIMENTAL_FEATURES: ${{ matrix.EXPERIMENTAL_FEATURES }}
COMPILER: ${{ matrix.COMPILER }}
ARCH: ${{ matrix.ARCH }}
COMPAT: ${{ matrix.COMPAT }}
CI: make sure we do a fuzzing build. Suggested-by: Christian Reitter. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-04-19 05:56:09 +02:00
FUZZING: ${{ matrix.FUZZING }}
gci: Split test configurations into groups We split into quick smoke-tests, normal-tests, and valgrind-tests. The first provides a quick-abort preventing overusing resources on what will be a failed run anyway.
2021-02-01 17:22:32 +01:00
PYTEST_PAR: ${{ matrix.PYTEST_PAR }}
PYTEST_OPTS: ${{ matrix.PYTEST_OPTS }}
NETWORK: ${{ matrix.NETWORK }}
TEST_CMD: ${{ matrix.TEST_CMD }}
TEST_GROUP_COUNT: ${{ matrix.TEST_GROUP_COUNT }}
TEST_GROUP: ${{ matrix.TEST_GROUP }}
run: |
bash -x .github/scripts/build.sh
- name: Upload Unit Test Results
if: always()
uses: actions/upload-artifact@v2
with:
name: Junit Report ${{ github.run_number }}.${{ matrix.cfg }}
path: report.*
valgrind-test:
name: Valgrind Test Config ${{ matrix.cfg }}
runs-on: ubuntu-20.04
needs: [smoke-test]
env:
DEVELOPER: 1
EXPERIMENTAL_FEATURES: 0
COMPAT: 1
TEST_GROUP_COUNT: 10
PYTEST_PAR: 3
strategy:
fail-fast: true
matrix:
include:
gci: Give each configuration an CFG value to identify them later We don't have a good way of referring to the configuration that failed, so let's give them a numberic ID. Particularly useful for the artifacts that'd be overwritten otherwise.
2021-01-23 11:55:52 +01:00
- {CFG: 9, VALGRIND: 1, TEST_GROUP: 1, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 10, VALGRIND: 1, TEST_GROUP: 2, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 11, VALGRIND: 1, TEST_GROUP: 3, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 12, VALGRIND: 1, TEST_GROUP: 4, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 13, VALGRIND: 1, TEST_GROUP: 5, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 14, VALGRIND: 1, TEST_GROUP: 6, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 15, VALGRIND: 1, TEST_GROUP: 7, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 16, VALGRIND: 1, TEST_GROUP: 8, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 17, VALGRIND: 1, TEST_GROUP: 9, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
- {CFG: 18, VALGRIND: 1, TEST_GROUP: 10, TEST_GROUP_COUNT: 10, PYTEST_PAR: 3}
gci: Add basic configuration for Github Actions as CI
2021-01-09 16:23:06 +01:00
steps:
- name: Checkout
uses: actions/checkout@v2.0.0
gci: Format the build script We were using a lot of docker conventions, which are not necessary in the script itself.
2021-01-19 12:02:02 +01:00
gci: Add basic configuration for Github Actions as CI
2021-01-09 16:23:06 +01:00
- name: Set up Python 3.6
uses: actions/setup-python@v2
with:
python-version: 3.6
- name: Install dependencies
run: |
gci: Move the setup and build steps into their own scripts We'd like to have some more structure to the tests, with smoke-tests going first, followed by valgrind and normal tests running in parallel. So to cut down on the copy-pasta we extract the scripts from the yaml, into their own files from where they can be easily invoked.
2021-02-01 17:09:40 +01:00
bash -x .github/scripts/setup.sh
gci: Add basic configuration for Github Actions as CI
2021-01-09 16:23:06 +01:00
- name: Build
gci: Expand matrix to include all CI configurations
2021-01-13 11:21:57 +01:00
env:
VALGRIND: ${{ matrix.VALGRIND }}
DEVELOPER: ${{ matrix.DEVELOPER }}
EXPERIMENTAL_FEATURES: ${{ matrix.EXPERIMENTAL_FEATURES }}
COMPILER: ${{ matrix.COMPILER }}
ARCH: ${{ matrix.ARCH }}
COMPAT: ${{ matrix.COMPAT }}
PYTEST_PAR: ${{ matrix.PYTEST_PAR }}
PYTEST_OPTS: ${{ matrix.PYTEST_OPTS }}
NETWORK: ${{ matrix.NETWORK }}
TEST_CMD: ${{ matrix.TEST_CMD }}
TEST_GROUP_COUNT: ${{ matrix.TEST_GROUP_COUNT }}
TEST_GROUP: ${{ matrix.TEST_GROUP }}
gci: Add basic configuration for Github Actions as CI
2021-01-09 16:23:06 +01:00
run: |
gci: Move the setup and build steps into their own scripts We'd like to have some more structure to the tests, with smoke-tests going first, followed by valgrind and normal tests running in parallel. So to cut down on the copy-pasta we extract the scripts from the yaml, into their own files from where they can be easily invoked.
2021-02-01 17:09:40 +01:00
bash -x .github/scripts/build.sh
gci: Upload the junit.xml report Can be used in a second stage to generate stats and detect flaky tests.
2021-01-21 19:54:50 +01:00
- name: Upload Unit Test Results
if: always()
uses: actions/upload-artifact@v2
with:
gci: Give each configuration an CFG value to identify them later We don't have a good way of referring to the configuration that failed, so let's give them a numberic ID. Particularly useful for the artifacts that'd be overwritten otherwise.
2021-01-23 11:55:52 +01:00
name: Junit Report ${{ github.run_number }}.${{ matrix.cfg }}
gci: Add the JSON report plugin to the ci configuration
2021-01-25 13:37:49 +01:00
path: report.*
Reference in New Issue Copy Permalink