Last updated on 2020-08-07 01:50:26 CEST.
| Package | FAIL | OK |
|---|---|---|
| ItemResponseTrees | 1 | 11 |
Current CRAN status: FAIL: 1, OK: 11
Version: 0.2.5
Check: tests
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:
<int> <dbl> <int> <dbl> <int> <dbl> <dbl>
1 5 5 4 1 5 1.37 0.900
2 4 4 5 3 4 0.951 0.711
3 3 2 4 5 1 -0.556 0.737
4 5 1 4 5 3 0.567 0.796
5 3 3 4 3 3 -0.261 0.647
6 4 4 2 4 5 0.712 0.770
7 4 3 5 4 4 0.952 0.689
8 4 3 4 4 4 0.547 0.671
9 4 3 5 4 4 0.952 0.689
10 5 3 5 4 4 1.32 0.729
# ... with 224 more rows
>
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 11.56 0.45 12.37 NA NA
> grDevices::dev.off()
null device
1
> ###
> ### Local variables: ***
> ### mode: outline-minor ***
> ### outline-regexp: "\\(> \\)?### [*]+" ***
> ### End: ***
> quit('no')
======== End of example output (where/before crash/hang up occured ?) ========
Flavor: r-oldrel-windows-ix86+x86_64