[Rd] Re: stop() and Rcmd (PR#910)
Thu, 12 Apr 2001 17:00:21 +0200 (MET DST)
On Thu, 12 Apr 2001, Prof Brian Ripley wrote:
> On Thu, 12 Apr 2001 firstname.lastname@example.org wrote:
> > "Rcmd check" on NT does not catch errors generated by stop() in files
> > in the tests directory. Thus the fact that all the tests complete does
> > not mean they completed succesfully.
In my experiments it *does* put out an error but continues. This is
intentional, as some Perls are rather flaky. If you want to change it,
remove the leading `-' in line 29 of etc/Makeconf-tests.
> > This report is based on output from Rcmd check for the bundle dseplus
> > version 2001.4-1. The test curve/tests/crvB07.R does a comparison which
> > on NT is outside of tolerance and executes stop(). (The comparison value
> > has been adjusted so that future versions of dseplus will not fail on
> > this test.)
> Perl version? (Lots of these things depend critically on the build.)
> Does make pkgcheck-foo work or not?
That does work for me, with build 613 (and at least 619-621 are known to
have broken system() calls).
If you are not seeing an error on the console as the tests run,
something else is up in your setup (not at all unlikely with
On the other hand, Rcmd check dse fails for me because the scripts
are asking for interactive input (the number of singular values) and
chewing up the rest of the script. That *is* a bug in dse.
In general, make pkgcheck-foo is more reliable under Windows.
BTW, this has nothing whatsoever to do with Rcmd!
Brian D. Ripley, email@example.com
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272860 (secr)
Oxford OX1 3TG, UK Fax: +44 1865 272595
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: firstname.lastname@example.org