CFLite seems to fail to download coverage data kept as an artifact about clusterfuzzlite HOT 8 CLOSED

@evverx - Jan said this was a one time mistake, we always try to reach reporter email directly. If this happen again, please do let us know.

from clusterfuzzlite.

I fixed it with

    cflite: pass token when fuzzers are built

diff --git a/.github/workflows/cflite_pr.yml b/.github/workflows/cflite_pr.yml
index 7a26df3..00f4d68 100644
--- a/.github/workflows/cflite_pr.yml
+++ b/.github/workflows/cflite_pr.yml
@@ -23,6 +23,7 @@ jobs:
       uses: google/clusterfuzzlite/actions/build_fuzzers@f05300d90afb3e43117ba235fb16597b50918b57
       with:
         sanitizer: ${{ matrix.sanitizer }}
+        github-token: ${{ secrets.GITHUB_TOKEN }}
     - name: Run Fuzzers (${{ matrix.sanitizer }})
       id: run
       uses: google/clusterfuzzlite/actions/run_fuzzers@f05300d90afb3e43117ba235fb16597b50918b57

so CFLite works as expected but the documentation needs updating.

from clusterfuzzlite.

Thanks a lot@evverx , can you please upload a PR for the doc change.

from clusterfuzzlite.

I'll push it to #76 a bit later.

from clusterfuzzlite.

Done

from clusterfuzzlite.

@inferno-chromium on an absolutely unrelated note, I wonder why messages like https://lists.freedesktop.org/archives/systemd-devel/2022-January/047284.html are sent to the systemd-devel mailing list?

from clusterfuzzlite.

@inferno-chromium on an absolutely unrelated note, I wonder why messages like https://lists.freedesktop.org/archives/systemd-devel/2022-January/047284.html are sent to the systemd-devel mailing list?

Sorry didn't know about this survey. I just emailed Jan to see if this can be sent to reporter email directly instead of project dev mailing list.

from clusterfuzzlite.

Thanks! It's good to know that there are bug hunters out there looking at systemd apparently.

from clusterfuzzlite.