-
Notifications
You must be signed in to change notification settings - Fork 566
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
Artifacts are no longer available for GitHub action runs #4654
Comments
Oof, I'll take a look into this. |
@jonathanmetzman, any update of this? I believe this causes all corpus updates from being discarded after each fuzz run, so every run starts with the same old corpus and corpuses no longer grow. |
Sorry I'll try to take a look today if I get a chance, I'm fairly busy with some other actively broken things though :-( |
@jonathanmetzman, any update on this? |
Need to upgrade npm package. We need to test this first by rebuilding the docker image. Fixes google/clusterfuzz#4654
Hopefully I'll land this early next week. Sorry for the delay and thank you for the reminders! |
Since January 30, artifacts such as corpuses, are no longer available for GitHub action runs, possibly due to GitHub's deprecation of v1, v2, and v3 of the artifact actions.
For example, for the ngtcp2 project, this run is the last one for which artifacts are available. For the following run they're not available.
This may also prevent corpuses from being updated by the runs, but I'm not sure.
The text was updated successfully, but these errors were encountered: