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.

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

Vitess fuzzers are broken #533

Open
dbussink opened this issue Dec 12, 2024 · 2 comments
Open

Vitess fuzzers are broken #533

dbussink opened this issue Dec 12, 2024 · 2 comments

Comments

@dbussink
Copy link

Currently the Vitess fuzzers are broken and have been for a while. There have been refactors on the Vitess end without realizing that they would affect things here.

I tried vitessio/vitess#17380, but it looks like there's copied set in this repository. I'm not sure how to test / fix that though.

@AdamKorcz Would you have any input / way to fix this here? Looks like you did most of the Vitess additions here?

@AdamKorcz
Copy link
Collaborator

Yes, I have been handling the Vitess fuzzers over several years. Ideally, they should live in the Vitess repository, such that changes to the Vitess source don't break the fuzz build. I will be happy to clean up all the fuzzers and migrate them upstream if you will accept the PRs.

@dbussink
Copy link
Author

Yes, I have been handling the Vitess fuzzers over several years. Ideally, they should live in the Vitess repository, such that changes to the Vitess source don't break the fuzz build. I will be happy to clean up all the fuzzers and migrate them upstream if you will accept the PRs.

That sounds like a good idea then to keep them in Vitess so it's easier to maintain and avoid regressions here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants