Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Reinstitute fuzzing once known parser issues are resolved #1843

Closed
ashutosh-narkar opened this issue Oct 14, 2019 · 3 comments
Closed

Reinstitute fuzzing once known parser issues are resolved #1843

ashutosh-narkar opened this issue Oct 14, 2019 · 3 comments
Labels
inactive investigating Issues being actively investigated

Comments

@ashutosh-narkar
Copy link
Member

We recently removed Fuzzit testing and Regression from the CI #1842.

If we plan to remove Fuzzit testing entirely, we need to clean it up from the README, Makefile, scripts etc.
@ashutosh-narkar ashutosh-narkar added the investigating Issues being actively investigated label Oct 14, 2019
@ashutosh-narkar ashutosh-narkar mentioned this issue Oct 14, 2019
Merged
@tsandall tsandall changed the title Remove Fuzzit testing and Regression Reinstitute fuzzing once known parser issues are resolved Oct 21, 2019
@tsandall
Copy link
Member

The fuzzit integration has been disabled because the fuzzer was running into a known issue in the generated parser. Once the underlying issue in the parser is resolved we could re-enable fuzzit.

tsandall added a commit to tsandall/opa that referenced this issue Oct 21, 2019
@tsandall
travis: Remove dead code related to fuzzer
70059c8 
Once the underlying parser issues are resolved, we can revisit the
fuzzit integration. Until then, it's not providing value for us.

Tracking issue: open-policy-agent#1843 (comment)

Signed-off-by: Torin Sandall <torinsandall@gmail.com>
@tsandall tsandall mentioned this issue Oct 21, 2019
Merged
tsandall added a commit that referenced this issue Oct 22, 2019
@tsandall
travis: Remove dead code related to fuzzer
57e8238 
Once the underlying parser issues are resolved, we can revisit the
fuzzit integration. Until then, it's not providing value for us.

Tracking issue: #1843 (comment)

Signed-off-by: Torin Sandall <torinsandall@gmail.com>
@patrick-east patrick-east mentioned this issue Jul 10, 2020
Closed
@stale
Copy link

stale bot commented Nov 22, 2021

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days.

@stale stale bot added the inactive label Nov 22, 2021
@srenatus
Copy link
Contributor

Oooold. We're now fuzzing in our nightly tests. With #4451, we'll use Go1.18's native fuzzing features.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
inactive investigating Issues being actively investigated
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bring back fuzzit patrick-east/opa
3 participants
@tsandall @srenatus @ashutosh-narkar