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.

Sign up for GitHub

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

Jump to bottom

Fuzzer artifacts don't always end up in the GCS bucket #32

Open
Ekleog opened this issue Jul 14, 2022 · 0 comments
Open

Fuzzer artifacts don't always end up in the GCS bucket #32

Ekleog opened this issue Jul 14, 2022 · 0 comments
Labels
GroomedA

Comments

@Ekleog
Copy link
Contributor

Ekleog commented Jul 14, 2022

Fuzzer crash crash-8a714d69410f54998ec3f0a22afd895a513a73d3 was not uploaded to GCS properly on host worker13, while in a fuzzing run that started 2022-07-12 21:29:55.495442.

Not adding more information as we did not investigate the issue itself yet, but we do need to figure out why sync logs don't make any mention of this hash, hinting at the fact that inotify for some reason did not pick it up at all.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
GroomedA
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Ekleog