Ci update

[billdenney]

Update CI to the latest versions (on top of #66)

[codecov]

Codecov Report

Base: 6.45% // Head: 6.45% // No change to project coverage 👍

Coverage data is based on head (afffa0c) compared to base (d970c98).
Patch has no changes to coverable lines.

❗ Current head afffa0c differs from pull request most recent head 963f73b. Consider uploading reports for the commit 963f73b to get more accurate results

Additional details and impacted files

@@          Coverage Diff          @@
##            main     #68   +/-   ##
=====================================
  Coverage   6.45%   6.45%           
=====================================
  Files          2       2           
  Lines         62      62           
=====================================
  Hits           4       4           
  Misses        58      58           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[billdenney]

@mattfidler, My best guess is that the issues go back to issues with the nlmixr2extra examples.

[billdenney]

@mattfidler, I think that the R-CMD-check issues may be related to memory issues. Only 7 GB of RAM are available: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources.

Any ideas how to slim down the memory use of CI?

[mattfidler]

Reduce the number of subjects for the estimates. But, that also makes it less useful as a metric for when nlmixr2 has something wrong with it...

[mattfidler]

You could also use the github ggPMX instead of commenting out the above.

[billdenney]

@mattfidler, If this completes with error 143 on the Linux and Mac R-CMD-check tests, then I think that it will be good to merge. It's better than what is currently in place.

The error 143 is related to running some example which is different than a general CI update. Those examples need to be identified and fixed, but that's a separate issue. This will get the pkgdown site building again which has not succeeded in a while.