This test trips an assertion when used with a debug-mode SpiderMonkey.
That is a separate bug that should be fixed, but for now, we should skip
the test when running under valgrind. The abort causes valgrind to think
that tons of memory are not freed, overrunning the useful output.

See #120.