Brilliant and so obviously correct. As per response a minute ago to Dirk's help, I agree completely and have started moves that look to be in line with that Dirk.
Apologies for my newbie/luser missteps and huge thanks to you both for your inputs. I'm awed to have had this. Chris ----- Original Message ----- > From: "Dirk Eddelbuettel" <e...@debian.org> > To: "Duncan Murdoch" <murdoch.dun...@gmail.com> > Cc: "Chris Evans" <chrish...@psyctc.org>, "r-package-devel" > <r-package-devel@r-project.org> > Sent: Tuesday, 16 March, 2021 12:45:44 > 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: > > 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 -- Small contribution in our coronavirus rigours: https://www.coresystemtrust.org.uk/home/free-options-to-replace-paper-core-forms-during-the-coronavirus-pandemic/ Chris Evans <ch...@psyctc.org> Visiting Professor, University of Sheffield <chris.ev...@sheffield.ac.uk> I do some consultation work for the University of Roehampton <chris.ev...@roehampton.ac.uk> and other places but <ch...@psyctc.org> remains my main Email address. I have a work web site at: https://www.psyctc.org/psyctc/ and a site I manage for CORE and CORE system trust at: http://www.coresystemtrust.org.uk/ I have "semigrated" to France, see: https://www.psyctc.org/pelerinage2016/semigrating-to-france/ https://www.psyctc.org/pelerinage2016/register-to-get-updates-from-pelerinage2016/ If you want an Emeeting, I am trying to keep them to Thursdays and my diary is at: https://www.psyctc.org/pelerinage2016/ceworkdiary/ Beware: French time, generally an hour ahead of UK. ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
