[RFC][PATCH] Rename Rakudo's "spectest_regression" to "spectest"
Patrick R. Michaud
pmichaud at pobox.com
Thu Oct 16 03:09:13 UTC 2008
On Fri, Oct 10, 2008 at 01:16:51PM -0700, chromatic wrote:
> On Friday 10 October 2008 06:45:16 jerry gay wrote:
>
> > during this week's design meeting, i mentioned that i think it's time
> > to rename 'spectest_regression' to 'test'. we didn't discuss it much,
> > but i imagine something like:
> >
> > test : coretest codetest spectest_regression
> >
> > with appropriate documentation changes.
>
> Please, no more coding standards tests run by default, unless you want to make
> a serious argument that someone who's never built Parrot or Rakudo before
> should really believe that the software may not work correctly if there's a
> trailing space in one file, or if the Subversion commit ID is missing from
> another file.
I think that Rakudo should follow Parrot in this respect -- if
Parrot's "make test" target runs the coding standards tests by
default, then Rakudo's should do so as well. The reason
why coding standards tests are run at all by Rakudo is because
we kept running into the situation where commits to Rakudo
would pass Rakudo's tests but then show up as failures when
someone else runs Parrot's "make test".
So, I'm +1 on removing the coding standards tests for Rakudo
if we can also eliminate them from Parrot's "make test".
(In reality, I'll do whatever the core Parrot team thinks we
ought to do here -- I just got tired of seeing Rakudo commits
generate failures in Parrot's "make test".)
Pm
More information about the parrot-dev
mailing list