On 16 March 2021 at 06:48, Duncan Murdoch wrote: | On 16/03/2021 5:58 a.m., Chris Evans wrote: | You have 5 workflows, and their current content doesn't appear to match | the results on your actions page. Pick one, run it, and I'll see if I | can spot the reason for a failure.
More granularly, one of these five workflow spawns nine builds of which the ones with older R version (3.3, 3.4, 3.5) fail as seen eg for run #3: https://github.com/cpsyctc/CECPfuns/actions/runs/657501549 Maybe you want to comment out runs for R versions that old, or debug why they fail. The error shown in R 3.5 (a version soon three years out of date you are not obliged to care for: CRAN uses only current, previous and next release) is not something I have seen before: ── R CMD build ───────────────────────────────────────────────────────────────── * checking for file ‘.../DESCRIPTION’ ... OK * preparing ‘CECPfuns’: * checking DESCRIPTION meta-information ... OK Error in parse_Rd("/tmp/RtmpydYbB0/Rbuild4d3e1cce5e37/CECPfuns/man/getCSC.Rd", : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' Execution halted Error: Error in proc$get_built_file() : Build process failed Calls: <Anonymous> ... build_package -> with_envvar -> force -> <Anonymous> Execution halted Error: Process completed with exit code 1. Here proce$get_built_file points to `pkgbuild` which is part of a non-CRAN toolchain. So this may not be caused by your package -- I can't tell. My preference is to keep it simpler: I usually get by with one workflow and generally at most two builds. Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
