* using log directory 'd:/Rcompile/CRANpkg/local/4.6/IssueTrackeR.Rcheck' * using R version 4.6.1 (2026-06-24 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 14.3.0 GNU Fortran (GCC) 14.3.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * current time: 2026-08-12 21:38:33 UTC * checking for file 'IssueTrackeR/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'IssueTrackeR' version '1.4.1' * package encoding: UTF-8 * 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 'IssueTrackeR' can be installed ... OK * checking installed package size ... OK * checking package 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 ... [1s] OK * checking whether the package can be loaded with stated dependencies ... [1s] OK * checking whether the package can be unloaded cleanly ... [1s] OK * checking whether the namespace can be loaded with stated dependencies ... [0s] OK * checking whether the namespace can be unloaded cleanly ... [1s] OK * checking loading without being on the library search path ... [1s] OK * checking whether startup messages can be suppressed ... [1s] 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 ... [4s] OK * checking Rd files ... [1s] OK * checking Rd metadata ... 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 examples ... [5s] OK * checking for unstated dependencies in 'tests' ... OK * checking tests ... [4s] ERROR Running 'spelling.R' [0s] Running 'testthat.R' [4s] 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") # nolint unused_import_linter undesirable_function_linter > library("IssueTrackeR") # nolint unused_import_linter undesirable_function_linter Currently, the default options are: - location for datasets is D:\temp\2026_08_12_01_50_00_15434\RtmpKc3O7K\data - owner: rjdverse - repo: rjdemetra Attaching package: 'IssueTrackeR' The following objects are masked from 'package:base': append, sample > > test_check("IssueTrackeR") Looking into closed_issues.yaml ... The issues will be read from D:\RCompile\CRANpkg\local\4.6\IssueTrackeR.Rcheck\tests\testthat\data\closed_issues.yaml. The labels will be read from D:\RCompile\CRANpkg\local\4.6\IssueTrackeR.Rcheck\tests\testthat\data\list_labels.yaml. The milestones will be read from D:\RCompile\CRANpkg\local\4.6\IssueTrackeR.Rcheck\tests\testthat\data\list_milestones.yaml. Saving _problems/test-bin_count-38.R Saving _problems/test-bin_count-39.R Saving _problems/test-bin_count-40.R Saving _problems/test-bin_count-41.R -- Issue jdemetra/jdplus-main#963 -- -- Issue jdemetra/jdplus-main#963 -- -- Issue jdemetra/jdplus-main#958 -- -- Issue jdemetra/jdplus-main#963 -- -- Issue jdemetra/jdplus-main#958 -- -- Issue jdemetra/jdplus-main#963 -- -- Issue jdemetra/jdplus-main#958 -- -- Issue jdemetra/jdplus-main#963 -- -- Issue jdemetra/jdplus-main#963 -- -- Issue jdemetra/jdplus-main#963 -- The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpKc3O7K\list_issues.yaml. The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpKc3O7K\list_labels.yaml. The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpKc3O7K\list_milestones.yaml. The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpKc3O7K\filec0ac3b8f2b68.yaml. The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpKc3O7K\datac0ac4bc919e8\object.yaml. The file already exists and won't be overwritten. To overwrite this file, please set `overwrite = TRUE`. [ FAIL 4 | WARN 0 | SKIP 3 | PASS 218 ] ══ Skipped tests (3) ═══════════════════════════════════════════════════════════ • On CRAN (3): 'test-get.R:2:5', 'test-get.R:32:5', 'test-update_database.R:4:5' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-bin_count.R:38:5'): bin_count works with different format ──── Expected `bin_count(obj_chr)` to be identical to `rep(c(1L, 2L, 0L), c(1L, 1L, 39L))`. Differences: `actual[39:42]`: 0 0 0 0 `expected[39:41]`: 0 0 0 ── Failure ('test-bin_count.R:39:5'): bin_count works with different format ──── Expected `bin_count(obj_date)` to be identical to `rep(c(1L, 2L, 0L), c(1L, 1L, 39L))`. Differences: `actual[39:42]`: 0 0 0 0 `expected[39:41]`: 0 0 0 ── Failure ('test-bin_count.R:40:5'): bin_count works with different format ──── Expected `bin_count(obj_POSIXct)` to be identical to `rep(c(1L, 2L, 0L), c(1L, 1L, 39L))`. Differences: `actual[39:42]`: 0 0 0 0 `expected[39:41]`: 0 0 0 ── Failure ('test-bin_count.R:41:5'): bin_count works with different format ──── Expected `bin_count(obj_POSIXlt)` to be identical to `rep(c(1L, 2L, 0L), c(1L, 1L, 39L))`. Differences: `actual[39:42]`: 0 0 0 0 `expected[39:41]`: 0 0 0 [ FAIL 4 | WARN 0 | SKIP 3 | PASS 218 ] Error: ! Test failures. Execution halted * checking PDF version of manual ... [18s] OK * checking HTML version of manual ... [6s] OK * DONE Status: 1 ERROR Check process probably crashed or hung up for 20 minutes ... killed Most likely this happened in the example checks (?), if not, ignore the following last lines of example output: The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpUztPL2\list_milestones.yaml. > > write_to_dataset(x = issues, dataset_dir = tempdir(), + dataset_name = "my_issues") The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpUztPL2\my_issues.yaml. > write_to_dataset(x = labels, dataset_dir = tempdir(), + dataset_name = "my_labels") The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpUztPL2\my_labels.yaml. > write_to_dataset(x = milestones, dataset_dir = tempdir(), + dataset_name = "my_milestones") The datasets will be exported to D:\temp\2026_08_12_01_50_00_15434\RtmpUztPL2\my_milestones.yaml. > > > > > ### *