it seems like a build of my package does not run a successful R-CMD-check github action, despite successful devtools::check(). I am kind of at a loss how to debug this.
Are there any hints on how to debug this just in general? What does the github action do differently than devtools::check()? Are similar cases already known?
I am happy to explain the procedure that builds the table that fails if that helps to solve the issue...
The installation failures occur because you have system dependencies missing (see the log) and you opted out of the automatic system dependency installation.
The failures that are common across platforms seem to be real problems with your package and probably don't have much to do with GitHub Actions. I see the same failures on my computer:
[ FAIL 4 | WARN 0 | SKIP 2 | PASS 102 ]
══ Skipped tests (2) ═══════════════════════════════════════════════════════════
• empty test (2): 'test_05_adb_data.R:5:1', 'test_05_adb_metadata.R:5:1'
══ Failed tests ════════════════════════════════════════════════════════════════
── Failure ('test_07_matchOntology.R:51:3'): ontology is correct after geometry normalisation ──
Check on 'onto@concepts$harmonised$has_broader_match' failed: Must be a set equal to {'NA','madeUp_2.3'}, but is missing elements {'madeUp_2.3'}
Backtrace:
▆
1. └─checkmate::expect_set_equal(...) at test_07_matchOntology.R:51:3
2. └─checkmate::makeExpectation(x, res, info, label)
[...]