Enable GitHub Actions checks

Author: HenrikBengtsson

.github/workflows/R-CMD-check.yaml

@@ -0,0 +1,110 @@
+on: [push, pull_request]
+  
+name: R-CMD-check
+
+jobs:
+  R-CMD-check:
+    if: "! contains(github.event.head_commit.message, '[ci skip]')"    
+
+    timeout-minutes: 30
+
+    runs-on: ${{ matrix.config.os }}
+
+    name: ${{ matrix.config.os }} (${{ matrix.config.r }}) ${{ matrix.config.label }}
+
+    strategy:
+      fail-fast: false
+      matrix:
+        config:
+          - {os: windows-latest, r: 'release'  }
+          - {os: windows-latest, r: 'oldrel'   }
+          - {os: macOS-latest,   r: 'release'  }
+          - {os: ubuntu-latest,  r: 'devel'    }
+          - {os: ubuntu-latest,  r: 'release'  }
+          - {os: ubuntu-latest,  r: 'oldrel'   }
+          - {os: ubuntu-latest,  r: '4.1'      }
+ 
+    env:
+      GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }}
+      R_KEEP_PKG_SOURCE: yes
+      R_REMOTES_NO_ERRORS_FROM_WARNINGS: true
+      ## Test in other locale (optional)
+      LANGUAGE: ${{ matrix.config.language }}
+      ## R (>= 4.4.0) Note, no trailing underscore (sic!)
+      _R_COMPARE_LANG_OBJECTS: eqonly
+      ## R CMD check
+      _R_CHECK_CRAN_INCOMING_: false
+      _R_CHECK_MATRIX_DATA_: true
+      _R_CHECK_SUGGESTS_ONLY_: true
+      _R_CHECK_THINGS_IN_TEMP_DIR_: true
+      _R_CHECK_TESTS_NLINES_: 300
+      RCMDCHECK_ERROR_ON: warning
+      ## Specific to futures
+      R_FUTURE_CONNECTIONS_ONMISUSE: "error[details=TRUE]"
+      R_FUTURE_GLOBALENV_ONMISUSE: "error"
+      R_FUTURE_GLOBALS_ONREFERENCE: "warning"
+      R_FUTURE_RNG_ONMISUSE: error
+      
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: r-lib/actions/setup-pandoc@v2
+
+      - uses: r-lib/actions/setup-r@v2
+        with:
+          r-version: ${{ matrix.config.r }}
+          http-user-agent: ${{ matrix.config.http-user-agent }}
+          use-public-rspm: true
+          
+      - uses: r-lib/actions/setup-r-dependencies@v2
+        with:
+          extra-packages: |
+            any::rcmdcheck
+            any::remotes
+          needs: check
+
+      - name: Install package itself (special case)
+        run: |
+          install.packages(".", repos = NULL, type = "source")  ## needed by parallel workers
+          
+        shell: Rscript {0}
+
+      - name: Session info
+        run: |
+          options(width = 100)
+          parallelly::availableCores(which = "all")
+          sapply(c(physical_cores = FALSE, logical_cores = TRUE), parallel::detectCores)
+          if (require(RhpcBLASctl, quietly=TRUE)) c(get_num_procs = get_num_procs(), get_num_cores = get_num_cores(), blas_get_num_procs = blas_get_num_procs(), omp_get_num_procs = omp_get_num_procs(), omp_get_max_threads = omp_get_max_threads())
+          capabilities()
+          pkgs <- installed.packages()[, "Package"]
+          sessioninfo::session_info(pkgs, include_base = TRUE)
+          ## Verify LANGUAGE settings by generating a translatable error
+          cat(sprintf("LANGUAGE=%s\n", sQuote(Sys.getenv("LANGUAGE"))))
+          cat(sprintf("locales: %s\n", sQuote(Sys.getlocale())))
+          tryCatch(log("a"), error = conditionMessage)
+        shell: Rscript {0}
+
+      - name: Check
+        if: runner.os != 'Windows'
+        run: |
+          rcmdcheck::rcmdcheck(
+            args = c("--no-manual", "--as-cran"),
+            check_dir = "check"
+          )
+        shell: Rscript {0}
+ 
+      - name: Check (Windows)
+        if: runner.os == 'Windows'
+        run: |
+          rcmdcheck::rcmdcheck(
+            args = c("--no-manual", "--as-cran", if (getRversion() >= "4.2.0") "--no-multiarch"),
+            check_dir = "check"
+          )
+        shell: Rscript {0}
+
+      - name: Upload check results
+        if: failure()
+        uses: actions/upload-artifact@v4
+        with:
+          name: ${{ runner.os }}-r${{ matrix.config.r }}-results
+          path: check

README.md

@@ -45,7 +45,7 @@ Because of this, it is important that you only join shared P2P cluster
 that you trust, i.e. where you trust all the P2P user and the user who
 hosts it such that they do not invite non-trusted or unknown users.
 
-There a mechanisms for launching P2P workers in _sandboxed_
+There are mechanisms for launching P2P workers in _sandboxed_
 environments. For instance, by running P2P workers in a sandboxed
 virtual machine (VM), in a sandboxed Linux container
 (e.g. [Apptainer], [Docker] and [Podman]), or via dedicated sandboxing

vignettes/future.p2p-10-getting-started.md

@@ -63,7 +63,7 @@ Because of this, it is important that you only join shared P2P cluster
 that you trust, i.e. where you trust all the P2P user and the user who
 hosts it such that they do not invite non-trusted or unknown users.
 
-There a mechanisms for launching P2P workers in _sandboxed_
+There are mechanisms for launching P2P workers in _sandboxed_
 environments. For instance, by running P2P workers in a sandboxed
 virtual machine (VM), in a sandboxed Linux container
 (e.g. [Apptainer], [Docker] and [Podman]), or via dedicated sandboxing