-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Closed
Description
While reviewing #10289 I noticed that the Restore Cached Corpus steps of the Fuzz jobs didn't have a single cache match. And most of the Save Corpus Cache steps failed with a warning like:
Warning: You've hit a rate limit, your rate limit will reset in 9 seconds
Failed to save: Unable to reserve cache with key corpus-cache-fuzz_non_utf8_paths, another job may be creating this cache.
Warning: Cache save failed.
I checked it with two additional PRs (#10417 and #10473) and there was the same picture.
Metadata
Metadata
Assignees
Labels
No labels