[R-pkg-devel] CRAN valgrind reports with zero leaks - actionable?

[Dirk Eddelbuettel]

Simon,

What you attempt to answer is not the relevant question (as Ivan concurred in
private email).  I can only invite you again to maybe venture to answer the
question I asked rather than belabor a point I didn't make (even if you fancy
lecturing on that one).

Lastly, as you may may missed it in two previous emails: this public post was
preceded by a private email that was also ignored, hence no repeat to private
email to cran using r-project.org.

Cheers,  Dirk



On 25 August 2022 at 09:57, Simon Urbanek wrote:
| Dirk,
| 
| as Ivan pointed out there is no indication that your package was flagged due to 0 byte leaks given other possible problems in the report which is likely why it is red, but we can't know since you didn't say, so it's all purely speculative. Given the total lack of details I wouldn't expect any further answer here unless you can provide those.
| 
| BTW: if you want an answer from CRAN, you should write to cran using R-project.org (I have not seen any mention of it there) since the actually relevant member may not see it otherwise.
| 
| Cheers,
| Simon
| 
| 
| > On 25/08/2022, at 8:12 AM, Dirk Eddelbuettel <edd using debian.org> wrote:
| > 
| > 
| > Dear CRAN Team,
| > 
| > On 18 August 2022 at 06:55, Dirk Eddelbuettel wrote:
| > | 
| > | [ Five days ago, I sent (most) of the message below to a CRAN team member. I
| > | have not had a reply, and it now appears that we are asked to email here so I
| > | am resending. ]
| > 
| > An answer would be much appreciated after the five initial days of this being
| > ignored as a private mail followed by a further six days of silence out here
| > in the open on this very list we once set up for help with packaging issues.
| > 
| > Can we ignore valgrind reports which show 'definitely lost: 0 bytes' ?
| > 
| > Curious,  Dirk
| > 
| > 
| > | A package of mine shows a valgrind report at with the details clearly
| > | indicating that no memory is lost: 
| > | 
| > |     ==3533933== LEAK SUMMARY:
| > |     ==3533933==    definitely lost: 0 bytes in 0 blocks
| > |     ==3533933==    indirectly lost: 0 bytes in 0 blocks
| > |     ==3533933==      possibly lost: 0 bytes in 0 blocks
| > | 
| > | The continuous integration setup for the package includes a nightly job
| > | against multiple version of the underlying C++ library to check just this.
| > | In those job we do NOT trigger an alert when, as here, zero bytes are
| > | reported lost.
| > | 
| > | Now, valgrind does report something possibly due (as the _Writing R
| > | Extensions_ manual notes) to compiler optimisation. So we currently consider
| > | this spurious.
| > | 
| > | Could CRAN let us know if this is considered a 'must fix' issue?  And if so,
| > | maybe so not show the alarmingly red 'valgrind' link to a report with zero leaks?
| > | 
| > | Many thanks as always for all these thorough tests.
| > | 
| > | Sincerely,  Dirk
| > | 
| > | 
| > | -- 
| > | dirk.eddelbuettel.com | @eddelbuettel | edd using debian.org
| > 
| > -- 
| > dirk.eddelbuettel.com | @eddelbuettel | edd using debian.org
| > 
| > ______________________________________________
| > R-package-devel using r-project.org mailing list
| > https://stat.ethz.ch/mailman/listinfo/r-package-devel
| > 
| 

-- 
dirk.eddelbuettel.com | @eddelbuettel | edd using debian.org