Thanks, Judd. It looks good. I think this was my (1) below. The (2) was to have a stub test whose only job is to check the PDL::Config and to display the values for test reports.
--Chris On 2/28/2011 4:25 PM, Judd Taylor wrote: > Chris, > > I've implemented your (2) below in the following test files (all modules > I'm maintaining): > > gd_oo_tests.t > gd_tests.t > > hdf_sd.t > hdf_vdata.t > hdf_vgroup.t > > gis_proj.t > proj_transform.t > proj_transform2.t > > This should fix the issues, as well as alternate issues that could come > up with from the same causes in any of the other test code I'm > maintaining. > > Let me know if I made some git mistake somewhere in there... > > Thanks, > Judd > > > > On Sun, 2011-02-27 at 09:01 -0500, Chris Marshall wrote: >> http://www.cpantesters.org/cpan/report/e1c8466e-4263-11e0-95a9-363986a4fa7b >> >> Some thoughts: >> >> (1) need to skip tests that weren't built >> (2) add a test to output the PDL::Config >> (3) modify tests to give better diagnostics >> >> I would like to see #1 and #2 in for PDL-2.4.8 >> release. PDL-2.4.7_010 is currently testing at >> >> PASS 95% >> FAIL ~1% (duplicate PDL install in path?) >> UNKNOWN ~4% (make -j3 -j3 in Known_problems) >> >> Cheers, >> Chris _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
