On Wed, Jun 29, 2005 at 08:37:44AM -0700, chromatic wrote: > On Wed, 2005-06-29 at 10:59 -0400, Matt Fowles wrote: > > > Would it be reasonable to not run tests that are known to leave core > > files? I feel like after a successful build there should not be > > evidence like this left around... > > People could set ulimit (though we'd have to tell them all to do that) > or Parrot::Test could have an END block that removes all core.* files > unless an environment variable is set.
You're making an assumption here about the name of core files, and where they are located. (Although setting ulimit -c above 0 on OS X is painful, given the size of the core files generated. So it's unlikely that parrot will be writing into /cores/ ) Nicholas Clark
