* using log directory 'd:/RCompile/CRANincoming/R-devel/maestro.Rcheck'
* using R Under development (unstable) (2024-08-23 r87049 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 13.2.0
    GNU Fortran (GCC) 13.2.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* checking for file 'maestro/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'maestro' version '0.2.0'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [10s] Note_to_CRAN_maintainers
Maintainer: 'Will Hipson <will.e.hipson@gmail.com>'
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking whether package 'maestro' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking 'build' directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking contents of 'data' directory ... OK
* checking data for non-ASCII characters ... OK
* checking LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking installed files from 'inst/doc' ... OK
* checking files in 'vignettes' ... OK
* checking examples ... OK
* checking for unstated dependencies in 'tests' ... OK
* checking tests ... [27s] ERROR
  Running 'testthat.R' [27s]
Running the tests in 'tests/testthat.R' failed.
Complete output:
  > # This file is part of the standard setup for testthat.
  > # It is recommended that you do not modify it.
  > #
  > # Where should you do additional test configuration?
  > # Learn more about the roles of various files in:
  > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview
  > # * https://testthat.r-lib.org/articles/special-files.html
  > 
  > library(testthat)
  > library(dplyr)
  
  Attaching package: 'dplyr'
  
  The following object is masked from 'package:testthat':
  
      matches
  
  The following objects are masked from 'package:stats':
  
      filter, lag
  
  The following objects are masked from 'package:base':
  
      intersect, setdiff, setequal, union
  
  > library(maestro)
  > library(future)
  > 
  > test_check("maestro")
  [ FAIL 2 | WARN 0 | SKIP 4 | PASS 183 ]
  
  ══ Skipped tests (4) ═══════════════════════════════════════════════════════════
  • On CRAN (4): 'test-build_schedule.R:10:3',
    'test-build_schedule_entry.R:14:3', 'test-run_schedule.R:151:3',
    'test-run_schedule.R:193:3'
  
  ══ Failed tests ════════════════════════════════════════════════════════════════
  ── Error ('test-suggest_orch_frequency.R:3:3'): suggest_orch_frequency gives valid suggestions ──
  Error in `suggest_orch_frequency(example_schedule)`: There are invalid time units.
  i Use `build_schedule()` to create a valid schedule.
  Backtrace:
      ▆
   1. ├─testthat::expect_equal(...) at test-suggest_orch_frequency.R:3:3
   2. │ └─testthat::quasi_label(enquo(object), label, arg = "object")
   3. │   └─rlang::eval_bare(expr, quo_get_env(quo))
   4. └─maestro::suggest_orch_frequency(example_schedule)
   5.   └─cli::cli_abort(c("There are invalid time units.", i = "Use {.fn build_schedule} to create a valid schedule."))
   6.     └─rlang::abort(...)
  ── Failure ('test-suggest_orch_frequency.R:46:3'): suggest_orch_frequency works when check_datetime is a Date ──
  Expected `suggest_orch_frequency(example_schedule, check_datetime = as.Date("2024-08-06"))` to run without any errors.
  i Actually got a <rlang_error> with text:
    There are invalid time units.
    i Use `build_schedule()` to create a valid schedule.
  
  [ FAIL 2 | WARN 0 | SKIP 4 | PASS 183 ]
  Error: Test failures
  Execution halted
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... OK
* checking re-building of vignette outputs ... OK
* checking PDF version of manual ... [14s] OK
* checking HTML version of manual ... OK
* DONE
Status: 1 ERROR