Howdy, I agree with Jim, it seems more "fulltest"-ish than "test"-ish to me.
Also, keep in mind that adding more things to "make test" could make our Travis continuous integration start timing out again, which will make various people sad, including me :) I also like the idea of a vote, but perhaps we can do it via email so more people can respond than just those that could make #ps ? Duke On Wed, Dec 5, 2012 at 7:34 PM, James E Keenan <jk...@verizon.net> wrote: > Today, in 53cf923e2, tests in ext/nqp-rx/t/nqp/ were added to the Parrot > distribution. > > Do we need to have these in the 'make test' target -- which means they > will be run each and every time someone tests Parrot? > > Or would it suffice to include them in the 'make fulltest' target? > > I'm leaning to the latter, in part because I really don't want to add to > the running time of 'test', and in part because I don't know whether they > will be significant enough indicators of breakage to warrant being run each > and every time. > > What do others think? (Dare I suggest we convene a parrotsketch for this? > ;-) ) > > Thank you very much. > Jim Keenan > > > > ______________________________**_________________ > http://lists.parrot.org/**mailman/listinfo/parrot-dev<http://lists.parrot.org/mailman/listinfo/parrot-dev> > -- Jonathan "Duke" Leto <jonat...@leto.net> Leto Labs LLC http://labs.leto.net 209.691.DUKE http://dukeleto.pl
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
