perf(cran): cut check time under 10 min via skip_on_cran (v0.9.153)#109
Merged
Conversation
…vy tests (v0.9.153) The 0.9.152 incoming pre-test was OK on Windows + Debian but was held for "Overall checktime 22 min > 10 min", dominated by the test suite (~12 min on Windows R-devel). skip_on_cran() the heavy integration / simulation / Shiny-app tests: the aqp-engine fallbacks (v0986/v0989), argic designation inference (v0990), the Monte-Carlo uncertainty suite (v0100), the benchmark suite (v09106), the argic-films audit (v0983), the sensitivity (v0942) / accuracy (v09107) / edge-case (v0937) / AfSP-routing (v0977) suites, and the Shiny-module testServer tests (v09101/02/03/150, shiny-pro-servers, benchmark-levels). They run in full on CI (NOT_CRAN=true). The fast unit tests, the 44 canonical fixtures and the end-to-end key tests still run on CRAN. No code or classification change. Local full R CMD check --as-cran (with vignettes + manual): testthat.R 526s -> 81s; Status 1 NOTE (the local-only html-tidy artefact). Estimated Windows total ~9 min, under the 10-min limit. cran-comments updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0.9.152 incoming pre-test was OK on Windows + Debian but was held for "Overall checktime 22 min > 10 min", dominated by the test suite (~12 min on Windows R-devel).
skip_on_cran()the heavy integration / simulation / Shiny-app tests (aqp-engine fallbacks, argic designation inference, Monte-Carlo uncertainty, benchmark suite, audits, sensitivity/accuracy/edge-case/AfSP suites, and thetestServerapp tests). They run in full on CI (NOT_CRAN=true); the fast unit tests, the 44 canonical fixtures and the end-to-end key tests still run on CRAN.No code or classification change. Local full
R CMD check --as-cran(with vignettes + manual): testthat.R 526s → 81s; Status 1 NOTE (the local-only html-tidy artefact). Estimated Windows total ~9 min, under the 10-min limit.🤖 Generated with Claude Code