02, 03, and 04 compile and execute C++/XS code for Inline consumption. 00load_prereqs.t -- verifies that all prerequisites are present that they load (including including CPP.pm itself). 01fn_cans.t -- Verify that all functions in CPP.pm can be called. Never fails. Useful when refactoring. 02basic.t -- Compiles basic C++ class code inline. 03prefix.t -- Compiles C++ code and tests the XS 'prefix' directive. 04charptr.t -- Verifies correct handling of c-strings as parameters or return values. 05pod.t -- Verifies the POD is reachable (optional). 06fn_regress.t -- Some regression-oriented tests I used while doing some refactoring. 07perlcritic.t -- Verifies the code is Perl::Critic friendly (author test, optional). 08cppguess.t -- Compares Makefile.PL compiler&library guesses with what ExtUtils::CppGuess would have guessed (optional).
Again, 02, 03, and 04 compile C++ code for Inline consumption. And those are the three test files that are failing on one of the Darwin smokers. Furthermore, as you've noticed, they fail before any tests get run. We're either crashing the C++ compiler, or crashing Perl as we invoke the XS code that Inline generated. It's only happening (so far) with that one Darwin smoker. There are a handful of Linux issues too, but my frequently-wrong senses persuaded me that the Darwin issue is lower hanging fruit than the Linux one. Dave On Sat, Apr 21, 2012 at 5:15 PM, Sisyphus <sisyph...@optusnet.com.au> wrote: > > ----- Original Message ----- From: "David Oswald" <daosw...@gmail.com> > To: <inline@perl.org> > Sent: Sunday, April 22, 2012 5:49 AM > Subject: Inline::CPP: New Darwin failure. > > > >> Inline::CPP version 0.38_004: >> >> I just noticed another Darwin smoke-test failure. >> >> PASS: >> http://www.cpantesters.org/cpan/report/c30eb71a-8bac-11e1-9ec4-a796756b88d3 >> FAIL: >> http://www.cpantesters.org/cpan/report/b5830500-89c8-11e1-9ec4-a796756b88d3 >> > > I notice that, in the failing test scripts, *none* of the tests get run. Can > you see any reason that those particular scripts (and not the others) should > fail to run the tests ? > > This is a bit like the "No subtests run" error that I see for some of the > test scripts in one of my modules. > I've compared my failing scripts with the scripts that run successfully, yet > cannot see anything that could trigger the "No subtests run" error. > > Cheers, > Rob -- David Oswald daosw...@gmail.com
