CRAN Package Check Results for Package vein

Last updated on 2020-10-07 07:50:25 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.9.0 25.73 188.05 213.78 OK
r-devel-linux-x86_64-debian-gcc 0.9.0 20.71 136.68 157.39 OK
r-devel-linux-x86_64-fedora-clang 0.9.0 268.71 OK
r-devel-linux-x86_64-fedora-gcc 0.9.0 256.46 OK
r-patched-linux-x86_64 0.9.0 22.65 173.53 196.18 OK
r-patched-solaris-x86 0.9.0 305.50 OK
r-release-linux-x86_64 0.9.0 23.12 173.28 196.40 OK
r-release-macos-x86_64 0.9.0 ERROR
r-release-windows-ix86+x86_64 0.9.0 43.00 230.00 273.00 OK
r-oldrel-macos-x86_64 0.9.0 ERROR
r-oldrel-windows-ix86+x86_64 0.9.0 49.00 283.00 332.00 OK

Additional issues

clang-ASAN LTO noOMP noOMP

Check Details

Version: 0.9.0
Check: whether package can be installed
Result: ERROR
    Installation failed.
Flavor: r-release-macos-x86_64

Version: 0.9.0
Check: examples
Result: ERROR
    Running examples in ‘vein-Ex.R’ failed
    The error most likely occurred in:
    
    > ### Name: check_nt
    > ### Title: Check the number of threads
    > ### Aliases: check_nt
    >
    > ### ** Examples
    >
    > {
    + check_nt()
    + }
    OMP: Error #15: Initializing libomp.dylib, but found libomp.dylib already initialized.
    OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://openmp.llvm.org/
Flavor: r-oldrel-macos-x86_64

Version: 0.9.0
Check: tests
Result: ERROR
     Running ‘testthat.R’ [23s/54s]
    Running the tests in ‘tests/testthat.R’ failed.
    Last 13 lines of output:
     [6] "Euro_LDV" "Proconve_HDV" "Euro_HDV" "PC_G" "LT"
    
     Range Year: 1980 2015
    
     Names of the Pollutants: CO HC NMHC CH4 NOx CO2 PM N2O
    
     Names of the ef data.frame:
     [1] "Age" "Year" "Pollutant" "Proconve_LDV" "t_Euro_LDV"
     [6] "Euro_LDV" "Proconve_HDV" "Euro_HDV" "PC_G" "LT"
    
     Range Year: 1980 2015
    
     Names of the Pollutants: CO HC NMHC CH4 NOx CO2 PM N2O
     OMP: Error #15: Initializing libomp.dylib, but found libomp.dylib already initialized.
     OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://openmp.llvm.org/
Flavor: r-oldrel-macos-x86_64