[R-pkg-devel] [CRAN-pretest-archived] CRAN Submission NMRphasing 1.0.6

[Duncan Murdoch]

On 2024-12-17 4:47 a.m., Aixiang Jiang wrote:
> Hi, team,
> 
> I am really confused by the error, which did not happen in the previous versions.
> 
> Since I have not changed my code at all, the possible reason is that the external function is changed. However, there is no error at all and all of my code runs successfully in my local machine.
> 
> So, how to solve the issue?

The rejection came because of the gcc-san check.  Those don't always 
show symptoms if you aren't running the same diagnostic tool, so this 
error could well have been present in earlier versions.

Looking at 
https://win-builder.r-project.org/incoming_pretest/NMRphasing_1.0.6_20241217_091411/specialChecks/gcc-san/summary.txt, 
I see that the error appears to have happened at 
MassSpecWavelet/src/find_local_maximum.c:492, i.e. line 492 of that 
file, which is writing outside the bounds of an allocated array.

I think that is coming from a package you are using, rather than from 
your package NMRphasing.  Maybe you can try working with the maintainer 
of that package to work out whether the problem is in it or in the way 
you are using it.

Duncan Murdoch

> 
> Thanks!
> Aixiang
> 
> ��ȡOutlook for Android<https://aka.ms/AAb9ysg>
> ________________________________
> From: ligges using statistik.tu-dortmund.de <ligges using statistik.tu-dortmund.de>
> Sent: Tuesday, December 17, 2024 12:43:05 AM
> To: Aixiang Jiang <aijiang using bccrc.ca>
> Cc: CRAN-submissions using R-project.org <CRAN-submissions using R-project.org>
> Subject: [CRAN-pretest-archived] CRAN Submission NMRphasing 1.0.6
> 
> CAUTION: EXTERNAL EMAIL. Verify both the sender's email and name. Avoid links/attachments unless expected. Report any suspicious message by forwarding it as an attachment to spammail using bccrc.ca
> 
> 
> Dear maintainer,
> 
> package NMRphasing_1.0.6.tar.gz does not pass the incoming checks automatically, please see the following pre-tests (additional issue checks):
> Windows: <https://win-builder.r-project.org/incoming_pretest/NMRphasing_1.0.6_20241217_091411/Windows/00check.log>
> Status: OK
> Debian: <https://win-builder.r-project.org/incoming_pretest/NMRphasing_1.0.6_20241217_091411/Debian/00check.log>
> Status: OK
> 
> Additional issues checked: <https://win-builder.r-project.org/incoming_pretest/NMRphasing_1.0.6_20241217_091411/specialChecks/>
> gcc-san: Status: 1 ERROR
> 
> Last released version's CRAN status: OK: 13
> See: <https://CRAN.R-project.org/web/checks/check_results_NMRphasing.html>
> 
> Last released version's additional issues:
>    gcc-ASAN <https://www.stats.ox.ac.uk/pub/bdr/memtests/gcc-ASAN/NMRphasing>
> 
> CRAN Web: <https://cran.r-project.org/package=NMRphasing>
> 
> 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/NMRphasing_1.0.6_20241217_091411/>
> The files will be removed after roughly 7 days.
> 
> No strong reverse dependencies to be checked.
> 
> Best regards,
> CRAN teams' auto-check service
> 
> 	[[alternative HTML version deleted]]
> 
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel