Testing nqp-rx against Parrot

François Perrad francois.perrad at gadz.org
Fri Jan 7 08:58:34 UTC 2011


2011/1/6 Patrick R. Michaud <pmichaud at pobox.com>

> Steps needed to test nqp-rx against Parrot:
>
> 1.  Build and install parrot
> 2.  Check out a clean copy of nqp-rx from
> http://github.com/perl6/nqp-rx.git
>    (or use 'make realclean' in an existing checkout)
> 3.  In the nqp-rx directory:
>        perl Configure.pl --parrot-config=$PARROT_INSTALL/bin/parrot_config
>        make test
>
> There should be no failures; as of 2011-01-06, nqp-rx's policy will
> be that there are no ongoing "known failures" in the nqp-rx test suite.
> If nqp-rx is known to be failing a given test, the test is either
> commented out or nqp-rx is fixed such that "make test" always shows
> no failures, unless the cause of the failure is something that is
> broken outside of nqp-rx itself.  ("make test" may show passing TODO's,
> however.)
>
> The total time needed to perform steps 2 and 3 on my system is less
> than 90 seconds.  Unlike Rakudo, nqp-rx does not require an overly
> large memory footprint to build and/or run.
>
>
with parrot & plumage installed,
   $ plumage test nqp-rx
does the job.

Note1: the Configure.pl embeds a 'make clean' which implies a rebuild at
each plumage invocation.
Note2: 'plumage clean nqp-rx' is now available.

François



> Pm
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20110107/a93c3555/attachment.html>


More information about the parrot-dev mailing list