Scalacheck eating exceptions

On Thu, Dec 15, 2011 at 7:00 AM, Daniel Sobral wrote:
> I was wondering why the range scalacheck tests were not detecting the
> bugs I knew were present in my code. I finally tracked it down to the
> exceptions produced by "error" in "class Counter" not being reported
> as failures! I'm not sure what to make of it, so I decided to report
> it while I consider the issue.

In the same department of no failures being reported, there's this
commit, which seems to have vanished in the move to git, I guess
because it only touched files in shootout.

https://lampsvn.epfl.ch/trac/scala/changeset/26090

Fixes for 3 tests which aren't failing.

Which should be failing, and would be failing if they were being
compiled by trunk, since they used methods which don't exist. Why aren't
they failing? That is the real mystery. In the interests of removing a
disincentive to track that one down, I future-proofed them against that
day when they start being run like they're supposed to be.