Gabor Szabo wrote: > > then it compiled. > I am not exactly sure what was the test result as it seems to have ran tests > in several directories and I did not go over all the output.
There is a section of the test output where it runs all the tests in the PDL-2.4.5/t/ directory and lists the results at the end looking something like this: ... t/trig........................ok t/ufunc.......................ok t/vaffine.....................ok t/xvals.......................ok All tests successful. Files=109, Tests=1155, 73 wallclock secs ( 0.16 usr 0.09 sys + 51.01 cusr 19.93 csys = 71.19 CPU) Result: PASS If you get that output, it means "tests pass". If you don't then the failing tests should be listed and you can report "all tests passed except xxx and yyy" and maybe cut and paste the output from the run of the test above the summary of results and the part with the listing of the failed tests. > Unfortunately some of the demo scripts are still blowing up... What demo scripts? Is this running perldl and then using the demo command? If so, which demos failed to run and did they pass the tests? Also, be sure you don't have another copy of PDL in your @INC when you are running the tests as that can result in mysterious and highly confusing failures... Cheers, Chris _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
