CRAN Package Check Results for Package lvmcomp

Last updated on 2020-08-07 01:49:51 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.2 90.70 34.88 125.58 OK
r-devel-linux-x86_64-debian-gcc 1.2 63.67 26.09 89.76 OK
r-devel-linux-x86_64-fedora-clang 1.2 178.46 OK
r-devel-linux-x86_64-fedora-gcc 1.2 151.27 OK
r-devel-windows-ix86+x86_64 1.2 204.00 86.00 290.00 OK
r-patched-linux-x86_64 1.2 66.32 34.36 100.68 OK
r-patched-solaris-x86 1.2 1991.20 ERROR
r-release-linux-x86_64 1.2 71.42 34.40 105.82 OK
r-release-macos-x86_64 1.2 OK
r-release-windows-ix86+x86_64 1.2 205.00 109.00 314.00 OK
r-oldrel-macos-x86_64 1.2 OK
r-oldrel-windows-ix86+x86_64 1.2 133.00 0.00 133.00 FAIL

Check Details

Version: 1.2
Check: examples
Result: ERROR
    Running examples in ‘lvmcomp-Ex.R’ failed
    The error most likely occurred in:
    
    > ### Name: StEM_mirt
    > ### Title: Stochastic EM algorithm for solving multivariate item response
    > ### theory model
    > ### Aliases: StEM_mirt
    >
    > ### ** Examples
    >
    > # run a toy example based on the M2PL model
    >
    > # load a simulated dataset
    > attach(data_sim_mirt)
    >
    > # generate starting values for the algorithm
    > A0 <- Q
    > d0 <- rep(0, J)
    > theta0 <- matrix(rnorm(N*K, 0, 1),N)
    > sigma0 <- diag(1, K)
    >
    > # do the confirmatory MIRT analysis
    > # to enable multicore processing, set parallel = T
    > mirt_res <- StEM_mirt(response, Q, A0, d0, theta0, sigma0)
    
    Step 1 |
    Step 2 |
    Step 3 |
    Step 4 |
    Step 5 |
    Step 6 |
    Step 7 |
    Step 8 |
    Step 9 |
    Step 10 |
    Step 11 |
    Step 12 |
    Step 13 |
    Step 14 |
    Step 15 |
    Step 16 |
Flavor: r-patched-solaris-x86

Version: 1.2
Check: for non-standard things in the check directory
Result: NOTE
    Found the following files/directories:
     ‘core’
Flavor: r-patched-solaris-x86

Version: 1.2
Check: running examples for arch ‘i386’
Result: FAIL
    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:
    
    ======== End of example output (where/before crash/hang up occured ?) ========
Flavor: r-oldrel-windows-ix86+x86_64