Skip to content

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

Description

@Ekleog

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions