make test/check ["changes in configure (for AIX; .....(PR#209)"]

[Martin Maechler]

If you have a few minutes time to help R development / testing,
*and* if have more than just a binary version of R, please read on..

>>>>> On Thu, 17 Jun 1999, Thomas Vogels <tov@infiniti.ece.cmu.edu> said:

      <....>

    ToV> "Kurt" == Kurt Hornik <Kurt.Hornik@ci.tuwien.ac.at> writes:
    Kurt> AIX is not a supported platform yet.

      <....>

    ToV> A final "make test" runs smoothly up to ../../tests/print-tests.R.
    ToV> There are some diffs with the length of printed doubles, like, <
    ToV> [4,] 1.7976931348623157e+308 ---
      >> [4,] 1.797693134862315708145e+308
    ToV> So the printed number in AIX is shorter?  Any comments?


I have been mainly responsible for  print-tests (and other "make test"s w/ R).
Already in the past we have realized that the C libraries which are
implementing printf() *are* quite different in their behavior, unfortunately.
The above difference is from formatC()'s output, and
formatC uses C-formatting (as its name might suggest..).

There are other places which might give C-library-dependent output.
Before I change  tests/print-tests.R (and ...Rout.save) again
(such that "make test" == "make check" runs to completion on AIX),
I'd be very glad if many of you R-users installers could run

    make check

	 [I think this will only work from the top-level of the
	  Source/Installation tree; i.e. is not available for those who 
	  only installed a binary distribution.
	  Redhat/SuSe Speak: you need SRPMS, not only RPMS]

and report --- to me, not all of R-devel ---
in case you DON'T get the final OK of the line
------------------------------------------------------------------------
Comparing `print-tests.Rout' to `./print-tests.Rout.save' ... OK
------------------------------------------------------------------------
	{{In case you don't get OK, please send me the WHOLE FILE
	  tests/Examples/print-tests.Rout.fail }}

Other problems of "make check" should also be reported, 
probably to R-devel maybe to R-bugs (which forwards to R-devel).

On the other hand, if make check runs to completion,
you get something like a benchmark (with all flaws of every benchmark)
of your computer's speed in running R:

  grep '^Time elapsed:' tests/Examples/base-Ex.Rout

              (almost the last line of tests/Examples/base-Ex.Rout)

will give you the CPU (and total..) Time that was needed to execute 
*all* examples in the R base package.

Thank you in advance!

Martin Maechler <maechler@stat.math.ethz.ch>	http://stat.ethz.ch/~maechler/
Seminar fuer Statistik, ETH-Zentrum SOL G1;	Sonneggstr.33
ETH (Federal Inst. Technology)	8092 Zurich	SWITZERLAND
phone: x-41-1-632-3408		fax: ...-1086			<><
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._