[Rd] Request for help with UBSAN and total absense of CRAN response
avraham.adler at gmail.com
Tue Jan 13 17:19:05 CET 2015
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 the package to
<http://win-builder.r-project.org/upload.aspx> and seeing if the CRAN
errors get created there, or is the problem CRAN shows on platforms
other than Windows?
On Tue, Jan 13, 2015 at 10:30 AM, Dirk Eddelbuettel <edd at debian.org> wrote:
> CRAN has a package of mine in upload limbo because it failed UBSAN.
> I am not entirely ignorant on the topic of sanitizers and SAN / ASAN / UBSAN;
> we created not one but two Docker containers with ASAN and USBAN:
> as well as predecessors to them in earlier Docker repos.
> Yet I fail to recreate the errors reported by CRAN:
> I asked politely (and twice) for help with the corresponding compiler
> configuration(s). But CRAN is of course way above communicating with mere
> mortals such as yours truly.
> So I have no recourse other than to spam all of you: if anybody here has a
> working UBSAN setup which can replicate the issue seen in the (rather small)
> RcppAnnoy package?
> Erik (upstream for Annoy, CC'ed) and I would be most grateful. We do not
> like being held hostage on an error report we cannot replicate and for which
> we do not receive any help (or even further communication) whatsoever.
> about to turn into yet another frustrated CRAN user
> http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
> R-devel at r-project.org mailing list
More information about the R-devel