[R-pkg-devel] Two (newbie/luser) questions about adding CI to github hosted package
georg|@bo@hn@kov @end|ng |rom m@nche@ter@@c@uk
Tue Mar 16 15:58:35 CET 2021
> ── R CMD build ─────────────────────────────────────────────────────────────────
> * 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.
The error seems to be in building the documentation. There used to be a buglet in older versions of R,
that caused some errors in processing to cause this kind of uninformative message from low level code.
I don't remember the R version but the time frame seems consistent.
It may well be that some \Sexpr code is spread over more than one line, which sometimes threw errors, sometimes silently ignored the lines after the first.
Maybe it's easiest just to require R >= "more recent version.
From: R-package-devel <r-package-devel-bounces using r-project.org> On Behalf Of Dirk Eddelbuettel
Sent: 16 March 2021 12:46
To: Duncan Murdoch <murdoch.duncan using gmail.com>
Cc: r-package-devel <r-package-devel using r-project.org>
Subject: Re: [R-pkg-devel] Two (newbie/luser) questions about adding CI to github hosted package
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:
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'
Error: Error in proc$get_built_file() : Build process failed
Calls: <Anonymous> ... build_package -> with_envvar -> force -> <Anonymous>
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.
https://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
More information about the R-package-devel