Skip to content
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

Open
amirlivneh opened this issue Jan 31, 2025 · 5 comments · May be fixed by google/oss-fuzz#13086
Open

Artifacts are no longer available for GitHub action runs #4654

amirlivneh opened this issue Jan 31, 2025 · 5 comments · May be fixed by google/oss-fuzz#13086
Assignees

Comments

@amirlivneh
Copy link

amirlivneh commented Jan 31, 2025

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.

@jonathanmetzman
Copy link
Collaborator

Oof, I'll take a look into this.

@jonathanmetzman jonathanmetzman self-assigned this Feb 4, 2025
@amirlivneh
Copy link
Author

@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.

@jonathanmetzman
Copy link
Collaborator

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 :-(

@amirlivneh
Copy link
Author

@jonathanmetzman, any update on this?

jonathanmetzman added a commit to google/oss-fuzz that referenced this issue Feb 21, 2025
Need to upgrade npm package.

We need to test this first by rebuilding the docker image.
Fixes google/clusterfuzz#4654
@jonathanmetzman jonathanmetzman linked a pull request Feb 21, 2025 that will close this issue
@jonathanmetzman
Copy link
Collaborator

Hopefully I'll land this early next week. Sorry for the delay and thank you for the reminders!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants