search

RMI-PACTA / actions

Actions for GitHub workflows
4 stars 0 forks source link

Assess which checks should be in the R CMD check matrix #12

Open jdhoffa opened 7 months ago

jdhoffa commented 7 months ago

Relates to https://github.com/RMI-PACTA/demo_actions/blob/main/.github/workflows/R-CMD-check.yml

We may want to decide which and how many versions of R, operating systems, etc. we want to check against.

Relates to RMI-PACTA/Actions#13

AlexAxthelm commented 7 months ago

As a note, we can define more than one matrix. one for "quick tests" to run on every push, and maybe an extended matrix to run in the merge queu (for repos that use that) or on main.

Not saying that's the right answer, but is an answer.

jdhoffa commented 7 months ago

Relates to https://github.com/RMI-PACTA/pacta.data.scraping/issues/38

Worth considering that the ubuntu-latest seems to fail on this repo because of a timeout limit (15min). ubuntu checks in general are likely to take a while given the lack of ubuntu binaries.

cjyetman commented 7 months ago

Relates to RMI-PACTA/pacta.data.scraping#38

Worth considering that the ubuntu-latest seems to fail on this repo because of a timeout limit (15min). ubuntu checks in general are likely to take a while given the lack of ubuntu binaries.

totally true... but I've been considering running a weekly R CMD check on repos I maintain so that a cached version of the ubuntu-latest runner image is available, which might mitigate this a bit. I think the problem is that if no Action has run in a while, every package that has been updated since then has to be installed and compiled. Hoping that running it weekly will limit the number of new package versions.

jdhoffa commented 7 months ago

That's a super clever solution! Very much back it, and in general in favour to keep the ubuntu-latest check if it's feasible