... and they didn't make it through. I put the files in a gist:
https://gist.github.com/djvanderlaan/1e9beb75d2d595824efc
Jan
On 16-01-15 15:21, Jan van der Laan wrote:
Dirk,
The vagrant setup I use to test my packages with UBSAN also seems to
replicate the error reported by CRAN
Dirk,
The vagrant setup I use to test my packages with UBSAN also seems to
replicate the error reported by CRAN (together with some other
warnings). I have attached the files (I hope they get through the
filters). I suppose you know what to do with them.
Jan
Dirk Eddelbuettel
On Tue, 2015-01-13 at 10:34 -0600, Dirk Eddelbuettel wrote:
On 13 January 2015 at 08:21, Dan Tenenbaum wrote:
| Where should the package source be downloaded from? I see it in CRAN (but
presumably the latest version that causes the issue is not yet downloadable)
and in github.
The
Hello, Dirk.
I have no experience with UBSAN etc., but as you mention not being
able to recreate the CRAN errors, it reminds me of the time I had
trouble getting my pacakge approved for CRAN as it passed all tets but
Win32, and I have a Win64 setup and could not test it. Have you tried
submitting
- Original Message -
From: Dirk Eddelbuettel e...@debian.org
To: r-devel@r-project.org
Cc: Erik Bernhardsson e...@malfunction.org, Dirk Eddelbuettel
e...@debian.org
Sent: Tuesday, January 13, 2015 7:30:47 AM
Subject: [Rd] Request for help with UBSAN and total absense of CRAN
On 13 January 2015 at 08:21, Dan Tenenbaum wrote:
| Where should the package source be downloaded from? I see it in CRAN (but
presumably the latest version that causes the issue is not yet downloadable)
and in github.
The presumable assumption is incorrect AFAIK.
The error should presumably
