Skip to content

Add an r-cmd-check-cpu-time skill - #80

Open
EmilHvitfeldt wants to merge 3 commits into
posit-dev:mainfrom
EmilHvitfeldt:add-r-cmd-check-cpu-time-skill
Open

Add an r-cmd-check-cpu-time skill#80
EmilHvitfeldt wants to merge 3 commits into
posit-dev:mainfrom
EmilHvitfeldt:add-r-cmd-check-cpu-time-skill

Conversation

@EmilHvitfeldt

@EmilHvitfeldt EmilHvitfeldt commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

If you have seen the following you know the pain that this skill tries to help you with.

* checking tests ... [48s/16s] NOTE
  Running ‘testthat.R’ [48s/15s]
Running R code in ‘testthat.R’ had CPU time 3.1 times elapsed time

I have spent so long time over the years dealing with this specific CRAN issue. We deal with it a lot because we have a lot of outside packages as dependencies.

Claude does a good job (when directed like this) to just chuck along, something that can be quite tedious when done manually

Registered in the r-lib plugin and listed in both the root and category READMEs.

Walks through diagnosing the R CMD check "had CPU time N times elapsed
time" NOTE: making the cpu/elapsed ratio visible, localizing the
offending test file or vignette on a threaded-BLAS Linux runner, and
capping threads at the call site.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant