[R-pkg-devel] Fwd: [CRAN-pretest-archived] CRAN submission huxtable 2.0.2

David Hugh-Jones davidhughjones at gmail.com
Wed Feb 7 14:14:13 CET 2018

Hi Dirk

Not running the test on CRAN would fix the problem, but it is kind of an
admission of failure. Part of CRAN's point is quality control, so switching
off tests just to pass seems perverse. I'll do it if that is the only

Yes, I bet the CRAN guys are highly busy, and full respect to them. It
might be nice, though, if there were a public document about what is on
those servers. Just e.g. a list of software and versions. Or the name of
the OS and release. That would presumably help
travis/win-builder/individual R developers to create environments closer to
the CRAN one, and that would reduce the number of CRAN-only bugs.


On 7 February 2018 at 12:20, Dirk Eddelbuettel <edd at debian.org> wrote:

> Maybe don't run the test if it always fails, and you cannot control the
> setting?
> Rcpp has had conditional tests for (I guess at least) 5+ years -- I just
> test
> if the version number has four components (ie, a test version) as
> opposed to three (ie 0.1.3, a release) and test only on the former (my box,
> Travis, ... but not CRAN). That started because CRAN had its time limit,
> but
> the idea is generally valid.
> | In general, is there any info available about the CRAN check servers? I
> | keep running into problems that are specific to them and cannot be
> | replicated on any other machine available to me.
> You can ask, and eventually someone will answer, but "those in charge" are
> busy too.
> Dirk
> --
> http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

	[[alternative HTML version deleted]]

More information about the R-package-devel mailing list