On 8 January 2019 at 21:31, Fellows, Ian wrote: | I have a package ( https://github.com/statnet/lolog | https://cran.r-project.org/web/packages/lolog/index.html ) that makes extensive use of Rcpp modules and passes module objects up and down between R and C++ regularly. I’ve used the package extensively in large simulation studies, and analyses where it has been stable. | | However, I have become aware of an intermittent failure to re-build the vignettes during R CMD check. I’ve only ever encountered the issue during check. Every once in a while I get WARNINGS like the following:
[...] | I’ve attempted to isolate the problem to something of a smaller but have thus far been unsuccessful. Since this only happens occasionally, I thought it might have something to do with how I’m passing objects up and down ( see for example: https://github.com/statnet/lolog/blob/master/inst/include/Model.h#L89 and https://github.com/statnet/lolog/blob/master/inst/include/util.h#L29 ), but that is just a shot in the dark. | | Does anyone have any insight as to how i might be able to better debug this or intuitions about what could be the cause? Is it possible to get a stack trace when rebuilding the vignettes? I do not. I have at times simplified, going as far as rendering the tex locally and shipping a not-really-vignette vignette that is just pdf. Which is of course a cop-out. That should be debug-able but one does not always get to the bottom ... Maybe someone else has a better idea. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
