-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CFLite seems to fail to download the latest builds due to "Bad credentials" #91
Comments
I "fixed" it by pointing CFLite to my fork of the clusterfuzzlite action where the latest "run-fuzzers" image was replaced with an image without google/oss-fuzz#7325: point run-fuzzers to an image where tokens are passed correctly
diff --git a/actions/run_fuzzers/action.yml b/actions/run_fuzzers/action.yml
index 1c21e9c..306cac9 100644
--- a/actions/run_fuzzers/action.yml
+++ b/actions/run_fuzzers/action.yml
@@ -58,7 +58,7 @@ inputs:
default: False
runs:
using: 'docker'
- image: 'docker://gcr.io/oss-fuzz-base/clusterfuzzlite-run-fuzzers:v1'
+ image: 'docker://gcr.io/oss-fuzz-base/clusterfuzzlite-run-fuzzers@sha256:71f56768b8b208928f568257d17bc33bbd1657359a126aef01ebbb4974dc5d70'
env:
FUZZ_SECONDS: ${{ inputs.fuzz-seconds }}
MODE: ${{ inputs.mode }} |
Lemme look into this, I think we changed this recently. |
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 22, 2022
The idea was to catch CFLite regressions but since the action itself pulls the latest docker images it can't be pinned properly and issues like google/clusterfuzzlite#91 are going to pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't break very often. Waiting for google/clusterfuzzlite#96
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 22, 2022
The idea was to catch CFLite regressions but since the action itself pulls the latest docker images it can't be pinned properly and issues like google/clusterfuzzlite#91 are going to pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't break very often. Waiting for google/clusterfuzzlite#96
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 22, 2022
The idea was to catch CFLite regressions but since the action itself pulls the latest docker images it can't be pinned properly and issues like google/clusterfuzzlite#91 are going to pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't break very often. Waiting for google/clusterfuzzlite#96
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 26, 2022
The idea was to catch CFLite regressions but since the action itself pulls the latest docker images it can't be pinned properly and issues like google/clusterfuzzlite#91 are going to pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't break very often.
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 26, 2022
The idea was to catch CFLite regressions but since the action itself pulls the latest docker images it can't be pinned properly and issues like google/clusterfuzzlite#91 are going to pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't break very often.
mrc0mmand
pushed a commit
to systemd/systemd
that referenced
this issue
Apr 26, 2022
The idea was to catch CFLite regressions but since the action itself pulls the latest docker images it can't be pinned properly and issues like google/clusterfuzzlite#91 are going to pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't break very often.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure why it stopped working but it appears CFLite can no longer download the latest builds. In https://github.com/evverx/elfutils/runs/5702214651?check_suite_focus=true it failed with
The latest builds can be found at https://github.com/evverx/elfutils/actions/runs/2041191178
The text was updated successfully, but these errors were encountered: