Skip to content

Add core limit for tests #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mrcaseb merged 3 commits into from
Aug 9, 2023
Merged

Add core limit for tests #47

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
27e7950
Add core limit for tests
tanho63 Aug 8, 2023
09599b1
Update setup.R
tanho63 Aug 8, 2023
3ff4eeb
Update tests/testthat/setup.R
tanho63 Aug 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions tests/testthat/setup.R
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# CRAN incoming checks can fail if examples use more than 2 cores.
# We can run in this problem by using data.table https://github.com/Rdatatable/data.table/issues/5658
# R CMD Check throws the NOTE because CRAN sets
# _R_CHECK_EXAMPLE_TIMING_CPU_TO_ELAPSED_THRESHOLD_ to "2.5"
# which means "more than two cores are running".
# We check for this specific environment variable and run the nflreadr helper
# if it is set to any value
cpu_threshold <- as.numeric(Sys.getenv("_R_CHECK_EXAMPLE_TIMING_CPU_TO_ELAPSED_THRESHOLD_",
NA_character_))

if (!is.na(cpu_threshold)) nflreadr::.for_cran()