>My only concern is that may betoo short and unlikely to find any bugs Remember: each time it starts from a random point. Apache Jenkins / Calcite-Master has 800+ builds now. Travis / Calcite has 2300+ builds now.
Just to clarify: current Travis configuration is 4 jobs (Java 8, 9, 10, 11) They take ~15 minutes to complete. We can add one more job that would be dedicated to fuzz testing, and we could configure it for 1..15 minutes. 2300 builds * 15 minutes is 23 days worth of fuzzing. >It seems like we could also possibly request a VM >from INFRA to run fuzz testing full time It would be great, however we need to have a fuzzer first :) Vladimir
