Michael>I wouldn't expect this to execute as part of the normal test suite
Note: we can include limited fuzzing in the regular test suite. For instance: a single Travis job that performs fuzz-only tests for a couple of minutes. That would not increase test duration, however it could eventually find a gem. We can even include a 5 second fuzzer into the regular suite, and it might dig 1000-10'000 cases or so provided we don't start PostgreSQL there. Michael>Either way, it sounds like this Michael> could be a good contribution if it's so adept at finding bugs :) Well, I even have a JIRA for that, however it takes time to add javadoc :) Here's one more case where fuzzer would definitely find issues: https://github.com/apache/calcite/pull/827 Vladimir
