Hi Tom, I'm seeing the failure(s) as well. I've put in a PR that hopefully addresses this issue - https://github.com/soh-cah-toa/p6-test-builder/pull/2.
While we're waiting for the author, you can try checkout out, and building https://github.com/dwarring/p6-test-builder.git Cheers, David On Thu, Apr 2, 2015 at 3:51 AM, Tom Browder <tom.brow...@gmail.com> wrote: > I need Perl 6 module Test::Builder to continue porting CPAN Perl 5 > module Geo::Ellipdoid to Perl 6. > > Test::Builder currently is in the Task::Star module but it fails > during the build process with Rakudo 2015.03 (it did NOT fail with > Rakudo 2015.02). > > I have filed a bug report at the github source repo > (https://github.com/soh-cah-toa/p6-test-builder), and have attempted > to contact the original author (Kevin Polulak, Email: > kpolu...@gmail.com, IRC: soh_cah_toa) with no success yet. > > The offending line with 'make test' is shown in the error message: > > ===SORRY!=== Error while compiling lib/Test/Builder/Plan.pm > Virtual call $.expected may not be used on partially constructed objects > at lib/Test/Builder/Plan.pm:102 > ------> alid or missing plan!' unless $.expected�.defined; > expecting any of: > prefix or term > make: *** [blib/lib/Test/Builder/Plan.pm.moarvm] Error 1 > > Then, when I comment out the offending line, I get this with 'make test': > > ===SORRY!=== Error while compiling lib/Test/Builder.pm > The following packages were stubbed but not defined: > Test::Builder > at lib/Test/Builder.pm:287 > ------> done unless $TEST_BUILDER.done_testing }�<EOL> > expecting any of: > statement end > make: *** [blib/lib/Test/Builder.pm.moarvm] Error 1 > > And I, a mere noob, have no idea how to proceed. I think that it will > take some careful study of the whole package to see how the class > constructors interrelate, but that will take some time. Could the > singleton use be the problem? > > In the meantime, does anyone have any idea what might have triggered > the failure between Rakudo 2015.02 and 2015.03? Were there any > significant changes in the class construction that might be a place to > look? Singleton use? > > I did re-visit at the Rakudo 2015.03 announcement and didn't notice > anything obvious that seemed to affect the modules involved. > > Final questions: > > 1. Am I the only person seeing this failure? > > 2. If the failure continues (assuming I'm not the only one, shouldn't > it be marked bad and removed from Task::Star? > > Thanks for any ideas. > > Cheers! > > -Tom >