CRAN incoming checks: CPU time XX times elapsed time

Package development
,
1

Dear Posit Package dev hive mind,

I am one of the maintainers for APCalign.

I'm currently preparing a resubmission to fix a few bugs that threatens the removal of our package.

Despite passing R CMD CHECK --as-cran locally, and on rhub on CRAN-like runners, I keep tripping
with an incoming check with Debian (log).

Flavor: r-devel-linux-x86_64-debian-gcc
Check: tests, Result: NOTE
Running 'testthat.R' [937s/57s]
Running R code in 'testthat.R' had CPU time 16.5 times elapsed time

This is intriguing for a few reasons:

  1. There is no parallel processing in our package code
  2. I cannot replicate this elsewhere
  3. It seems to be only on Debian

I found Dirk Eddelbuettel's very thorough solution to managing code that uses more than one CPU on CRAN however, I am hesitant in implementing this because of the reasons above.

Would an R-package-fairy-god-mother have any kind words of advice to reproduce the note and show me a trick or two to manage it please?

Confused and grateful,

Fonti