I submitted a minor update of cubature (suggesting rmarkdown for vignettes) and received a message that the package generated warnings. However, the warnings were noted to be untrustworthy (see email below). I noted this in the submission comments as well as the reply to the auto-check email.
It appears that I am unable to get beyond the auto-check service. Any suggestions? -Naras -------- Forwarded Message -------- Subject: Re: [CRAN-pretest-archived] CRAN submission cubature 2.0.4.2 Date: Thu, 6 May 2021 12:51:37 -0700 From: Balasubramanian Narasimhan <na...@stanford.edu> To: cran-submissi...@r-project.org, na...@stat.stanford.edu Dear CRAN, As explained in my submission comment, the warning is noted to be flaky in the message below. Thank you. -Naras On 18/03/2021 13:05, Kurt Hornik wrote: >>>>>> Uwe Ligges writes: > >> Dear Naras, >> your package cubature shows compiler warnings under Windows: >> <https://cran.r-project.org/web/checks/check_results_cubature.html> > >> Any chance getting rid of these? Please try and resubmit. > > Interestingly, r-release-macos shows this too ... I think -Warray-bounds is known to be flaky in earlier compilers. I do not see this on macOS with Apple Clang 11.5 (latest for High Sierra) or 12.4 (current) and nor does Tomas for GCC 10 on Windows. -- Brian D. Ripley, rip...@stats.ox.ac.uk Emeritus Professor of Applied Statistics, University of Oxford On 5/6/21 12:27 PM, lig...@statistik.tu-dortmund.de wrote: > Dear maintainer, > > package cubature_2.0.4.2.tar.gz does not pass the incoming checks > automatically, please see the following pre-tests: > Windows:<https://win-builder.r-project.org/incoming_pretest/cubature_2.0.4.2_20210506_211603/Windows/00check.log> > Status: 1 WARNING > Debian:<https://win-builder.r-project.org/incoming_pretest/cubature_2.0.4.2_20210506_211603/Debian/00check.log> > Status: OK > > Last released version's CRAN status: WARN: 3, NOTE: 10 > See:<https://CRAN.R-project.org/web/checks/check_results_cubature.html> > > CRAN Web:<https://cran.r-project.org/package=cubature> > > Please fix all problems and resubmit a fixed version via the webform. > If you are not sure how to fix the problems shown, please ask for help on the > R-package-devel mailing list: > <https://stat.ethz.ch/mailman/listinfo/r-package-devel> > If you are fairly certain the rejection is a false positive, please reply-all > to this message and explain. > > More details are given in the directory: > <https://win-builder.r-project.org/incoming_pretest/cubature_2.0.4.2_20210506_211603/> > The files will be removed after roughly 7 days. > > *** Strong rev. depends ***: ALTopt apTreeshape bivquant BNSP calibrator > clusteredinterference coga cold dbmss DRAYL dvmisc ei equivalenceTest > fMultivar GAS GB2 GPCMlasso GRCdata highfrequency hyper2 ICAOD inctools > MCMCglmm MIRES MMDCopula MWright NonNorMvtDist np OBASpatial ODS optimStrat > PCMRS planar pooling Power2Stage PowerTOST ProFit QGglmm robustlmm skedastic > SphericalCubature spNetwork statsr SurvDisc symmoments TCIU tseriesEntropy > UPCM vines WLinfer yuima > > Best regards, > CRAN teams' auto-check service > > Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64 > Check: CRAN incoming feasibility, Result: Note_to_CRAN_maintainers > Maintainer: 'Balasubramanian Narasimhan<na...@stat.stanford.edu>' > > Flavor: r-devel-windows-ix86+x86_64 > Check: whether package can be installed, Result: WARNING > Found the following significant warnings: > ./src/common/Random.c:105:5: warning: 'memcpy' pointer overflow between > offset 0 and size [4294967292, 2147483647] [-Warray-bounds] > ./src/common/Random.c:105:5: warning: 'memcpy' pointer overflow between > offset 0 and size [-4, 9223372036854775807] [-Warray-bounds] > See 'd:/RCompile/CRANincoming/R-devel/cubature.Rcheck/00install.out' for > details. [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
