diff options
| author | Evgeny Vereshchagin <evvers@ya.ru> | 2022-01-30 09:18:53 +0000 |
|---|---|---|
| committer | Evgeny Vereshchagin <evvers@ya.ru> | 2022-01-30 10:17:25 +0000 |
| commit | d38363b96b763c48aa1fc7742db7d17301d48ced (patch) | |
| tree | d58b89ad660ea326a26ae0a56612fb982877f6ed | |
| parent | 69aa4982bc514a1d096aeb0563025ece81f978f9 (diff) | |
| download | systemd-d38363b96b763c48aa1fc7742db7d17301d48ced.tar.gz | |
ci: no longer upload the latest builds on commits
The idea behind this action is to make it possible to compare the
latest fuzz targets with PRs to figure out whether bugs are really
reproducible in PRs only. Since forks (including systemd-stable) are
usually based on the upstream repository where almost all the bugs
are fixed before releases are cut it should be safe to assume that
if CFLite finds bugs in PRs they are most likely introduced in those
PRs.
It should probably be brought back once https://github.com/google/clusterfuzzlite/issues/84
is fixed.
| -rw-r--r-- | .github/workflows/cflite_build.yml | 31 |
1 files changed, 0 insertions, 31 deletions
diff --git a/.github/workflows/cflite_build.yml b/.github/workflows/cflite_build.yml deleted file mode 100644 index cfb3721a0e..0000000000 --- a/.github/workflows/cflite_build.yml +++ /dev/null @@ -1,31 +0,0 @@ ---- -# vi: ts=2 sw=2 et: -# SPDX-License-Identifier: LGPL-2.1-or-later -# -name: ClusterFuzzLite continuous builds -on: - push: - branches: - - main - - v[0-9]+-stable - -permissions: read-all - -jobs: - Build: - runs-on: ubuntu-latest - if: github.repository != 'systemd/systemd' - concurrency: - group: ${{ github.workflow }}-${{ matrix.sanitizer }}-${{ github.ref }} - cancel-in-progress: true - strategy: - fail-fast: false - matrix: - sanitizer: [address, undefined, memory] - steps: - - name: Build Fuzzers (${{ matrix.sanitizer }}) - id: build - uses: google/clusterfuzzlite/actions/build_fuzzers@41dccd0566905e2a7d1724e7883edbfa66d78877 - with: - sanitizer: ${{ matrix.sanitizer }} - upload-build: true |