syz-ci: gzip programs coverage on GCS #5852
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tarasmadan
force-pushed
the
gzip-coverage-export
branch
3 times, most recently
from
f860164 to
2ba116b
Compare
tarasmadan
force-pushed
the
gzip-coverage-export
branch
6 times, most recently
from
7870117 to
54f0c71
Compare
a-nogikh
reviewed
Mar 25, 2025
tarasmadan
force-pushed
the
gzip-coverage-export
branch
from
54f0c71 to
c6b97d0
Compare
a-nogikh
reviewed
Mar 25, 2025
tarasmadan
force-pushed
the
gzip-coverage-export
branch
2 times, most recently
from
9b47664 to
5190f1e
Compare
Each fuzzing session costs 2G-13G now. It looks too much. The data is highly redundant (jsonl) thus compression should help.
tarasmadan
force-pushed
the
gzip-coverage-export
branch
from
5190f1e to
6eb1d4d
Compare
ramosian-glider
approved these changes
Mar 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Each fuzzing session costs 2G-13G of detailed coverage data now. It looks too much.
The data is highly redundant (jsonl) thus compression should help.
P. S. The better option is to dedup this data in some DB but it will take much more efforts.
Cloud Spanner allows to import gzipped JSONL data just in case we'll decide to use these programs for web UX.
TODO: