• using R Under development (unstable) (2026-07-22 r90289)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 22.1.8 (1+b1)     Debian flang version 22.1.8 (1+b1)
• running under: Debian GNU/Linux forky/sid
• using session charset: UTF-8 * current time: 2026-07-24 00:11:46 UTC
• checking for file ‘envnames/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘envnames’ version ‘0.4.1’
• checking CRAN incoming feasibility ... [2s/2s] NOTE Maintainer: ‘Daniel Mastropietro <mastropi@uwalumni.com>’ No Authors@R field in DESCRIPTION. Please add one, modifying   Authors@R: person(given = "Daniel",                     family = "Mastropietro",                     role = c("aut", "cre"),                     email = "mastropi@uwalumni.com") as necessary.
• 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 executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking serialization versions ... OK
• checking whether package ‘envnames’ can be installed ... OK See the install log for details.
• used C compiler: ‘Debian clang version 22.1.8 (1+b1)’
• 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 ... [0s/0s] OK
• checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the package can be unloaded cleanly ... [0s/0s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
• checking loading without being on the library search path ... [0s/0s] 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 ... [7s/8s] OK
• checking Rd files ... [1s/1s] 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 line endings in C/C++/Fortran sources/headers ... OK
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... OK
• checking sizes of PDF files under ‘inst/doc’ ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [3s/4s] OK
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [31s/37s] ERROR   Running ‘testthat.R’ [31s/37s] Running the tests in ‘tests/testthat.R’ failed. Complete output:   > library(testthat)   > library(envnames)   >   > test_check("envnames")      Environments involved:   Current environment: <environment: R_GlobalEnv>   Parent environment of env1: <environment: R_GlobalEnv>   Parent environment of env2: <environment: R_GlobalEnv>   Parent environment of env11: <environment: 0x55864bce3bf0>   R_GlobalEnv env_of_envs envir        "env2" "env2" "env2"   correct memory address: <0x55865238fcb8>   observed result: TRUE   Saving _problems/test-get_env_names-25.R   Saving _problems/test-get_env_names-158.R   Now inside function g   Environment name of calling function (using environmentName() function): ""   Environment name of calling function as returned by get_fun_calling(): env1$f   Now inside function g   Environment name of calling function (using environmentName() function): ""   Environment name of calling function as returned by get_fun_calling(): testenv$f   Now inside function g   Environment name of calling function (using environmentName() function): ""   Environment name of calling function as returned by get_fun_calling(): f   [ FAIL 2 | WARN 10 | SKIP 8 | PASS 308 ]      ══ Skipped tests (8) ═══════════════════════════════════════════════════════════   • 2018/10/10: This test works fine if run OUTSIDE the test_that() call, (1):     'test-environment_name.r:211:3'   • On CRAN (1): 'test-obj_find.r:364:3'   • This gives 'node stack overflow' error in 32-bit platform... apparently     meaning that there is a recursive call that does not end... (1):     'test-environment_name.r:167:3'   • This test fails on CRAN (1): 'test-get_obj_address.r:214:3'   • This test gives different results when running in TEST mode and when running     in CHECK mode, and it fails when testing the package in     https://win-builder.r-project.org/ which is the real test before package     submission to CRAN. (1): 'test-get_obj_address.r:59:3'   • no longer true: we now return always NULL for strings (1):     'test-get_obj_address.r:267:3'   • the is_memory_address() function was changed to accept any number of digits     between 8 and 16, (1): 'test-functions.r:148:3'   • this cannot be tested because the call is inside function test_that()! (1):     'test-get_fun_calling_chain.r:58:3'      ══ Failed tests ════════════════════════════════════════════════════════════════   ── Failure ('test-get_env_names.r:25:3'): T0a) the table returned only contains system/package environments AND the empty environment             when no user environments are defined, except for the user environments defined in the envnames package ──   Expected `observed` to equal `expected`.   Differences:   Lengths differ: 22 is not 21   ── Failure ('test-get_env_names.r:158:5'): T1) the default behaviour is the expected one, i.e. all environments (user and packages)              in the whole workspace are retrieved.              User-defined environments are found in both the global environment and packages.              The search is recursive on all user-defined environments found.              This is the default behaviour and should be obtained when envir=NULL.              Note that we do NOT compare the info about function execution environments              because the expected value for is too complicated to write. ──   Expected `observed` to equal `expected_check`.   Differences:   Attributes: < Component "row.names": Numeric: lengths (29, 28) differ >   Component "type": Lengths (29, 28) differ (string compare on first 28)   Component "type": 3 string mismatches   Component "location": Lengths (29, 28) differ (string compare on first 28)   Component "location": 'is.NA' value mismatch: 21 in current 20 in target   Component "locationaddress": Lengths (29, 28) differ (string compare on first 28)   Component "locationaddress": 'is.NA' value mismatch: 21 in current 20 in target   Component "address": Lengths (29, 28) differ (string compare on first 28)   Component "address": 21 string mismatches   ...      [ FAIL 2 | WARN 10 | SKIP 8 | PASS 308 ]   Error:   ! Test failures.   Execution halted
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [12s/14s] OK
• checking PDF version of manual ... [6s/8s] OK
• checking HTML version of manual ... [2s/2s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 1 ERROR, 1 NOTE