nqp-rx tests: in 'make test' or in 'make fulltest'

Jonathan "Duke" Leto jonathan at leto.net
Thu Dec 6 20:20:42 UTC 2012


Howdy,

I didn't see Reini's explanation before my previous email. With that input,
as long as it doesn't make Travis timeout, I don't have a strong opinion.

Duke

On Thu, Dec 6, 2012 at 12:19 PM, Jonathan "Duke" Leto <jonathan at leto.net>wrote:

> 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 <jkeen at 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 <jonathan at leto.net>
> Leto Labs LLC http://labs.leto.net
> 209.691.DUKE http://dukeleto.pl
>



-- 
Jonathan "Duke" Leto <jonathan at leto.net>
Leto Labs LLC http://labs.leto.net
209.691.DUKE http://dukeleto.pl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20121206/12c19515/attachment.html>


More information about the parrot-dev mailing list