Update OSS-Fuzz Scripts to Use New QA-Assets Repo Structure#1913

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

Byron merged 1 commit intogitpython-developers:mainfromDaveLak:refactor-oss-fuzz-scripts-to-use-new-qa-assets-repo-layout

May 8, 2024

Merged

Update OSS-Fuzz Scripts to Use New QA-Assets Repo Structure#1913

Byron merged 1 commit intogitpython-developers:mainfromDaveLak:refactor-oss-fuzz-scripts-to-use-new-qa-assets-repo-layout

May 8, 2024

Conversation

Copy link

Contributor

DaveLak commentedMay 8, 2024•
edited
Loading

merginggitpython-developers/qa-assets#2 should be coordinated with merging this PR.

This change is required to support the changes to the seed data repo structure introduced in:
gitpython-developers/qa-assets#2

This moves most of the seed data related build steps into the OSS-Fuzz Docker image build viacontainer-environment-bootstrap.sh. This includes moveing the dictionaries into that repo.

The fuzzing/README.md here should be updated in a follow-up with a link to the qa-assets repo (and probably some context setting about corpora in general) but I have opted to defer that as I think the functionality added by the seed data improvements is valuable as is and shouldn't be blocked by documentation writers block.

Update OSS-Fuzz Scripts to Use New QA-Assets Repo Structure

2cfd200

This change is required to support the changes to the seed data repostructure introduced in:gitpython-developers/qa-assets#2This moves most of the seed data related build steps into the OSS-FuzzDocker image build via `container-environment-bootstrap.sh`. Thisincludes moveing the dictionaries into that repo.The fuzzing/README.md here should be updated in a follow-up with a linkto the qa-assets repo (and probably some context setting about corporain general) but I have opted to defer that as I think the functionalityadded by the seed data improvements is valuable as is and shouldn't beblocked by documentation writers block.