On Fri, Jan 23, 2009 at 11:07 AM, Jonathan Worthington <[email protected]> wrote: > Will Coleda wrote: >> >> Why we can't just run this test via t/harness? >> >> > > That's exactly what the patch does: > >>> + $(PERL) t/harness $(EXTRA_TEST_ARGS) -r t/op/annotate.t >>> > > Or am I missing the point? But just feel free, to commit whatever better way > you want - the aim is just to run this test also in > compile-to-bytecode-first mode on make test, as well as in the normal "just > run it" way. > > Thanks, > > Jonathan > >
Ok, so the -r makes it hard to run as part of the single invocation of t/harness that we do with 'make test' Why do we have to run this one test with -r when we run 'make test'? Why not catch it with 'make testr' which is run as part of 'make fulltest'? -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
