When running jsfunfuzz with the harness on Windows, sometimes it spews lots of "jsfunfuzz didn't finish" errors. Since we don't ever look at these errors, perhaps we should mark them as "uninteresting", by bumping up the minimum interesting level to report to FuzzManager.
Right now it's blocked by a bucket in FuzzManager.
When running jsfunfuzz with the harness on Windows, sometimes it spews lots of "jsfunfuzz didn't finish" errors. Since we don't ever look at these errors, perhaps we should mark them as "uninteresting", by bumping up the minimum interesting level to report to FuzzManager.
Right now it's blocked by a bucket in FuzzManager.