Last updated on 2023-08-31 08:01:24 CEST.
| Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
|---|---|---|---|---|---|---|
| r-devel-linux-x86_64-debian-clang | 2.4.0 | 21.63 | 313.39 | 335.02 | OK | |
| r-devel-linux-x86_64-debian-gcc | 2.4.0 | 21.85 | 222.28 | 244.13 | OK | |
| r-devel-linux-x86_64-fedora-clang | 2.4.0 | 411.40 | OK | |||
| r-devel-linux-x86_64-fedora-gcc | 2.4.0 | 392.39 | OK | |||
| r-devel-windows-x86_64 | 2.4.0 | 25.00 | 263.00 | 288.00 | OK | |
| r-patched-linux-x86_64 | 2.4.0 | 30.20 | 293.34 | 323.54 | OK | |
| r-release-linux-x86_64 | 2.4.0 | 20.53 | 301.89 | 322.42 | OK | |
| r-release-macos-arm64 | 2.4.0 | 113.00 | OK | |||
| r-release-macos-x86_64 | 2.4.0 | 248.00 | OK | |||
| r-release-windows-x86_64 | 2.4.0 | 33.00 | 0.00 | 33.00 | FAIL | |
| r-oldrel-macos-arm64 | 2.4.0 | 103.00 | OK | |||
| r-oldrel-macos-x86_64 | 2.4.0 | 135.00 | OK | |||
| r-oldrel-windows-x86_64 | 2.4.0 | 33.00 | 0.00 | 33.00 | FAIL |
Version: 2.4.0
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:
4 aU 1131.690 1248.630 K67MR007
5 aI 1460.310 1650.440 K67MR007
6 aI 621.437 767.500 K67MR009
7 aU 1540.940 1685.690 K67MR009
8 OY 1914.810 2007.940 K67MR009
9 OY 1021.440 1142.440 K67MR011
10 aI 2206.560 2328.500 K67MR011
> ## Not run: write.emusegs(dip, "write.emusegs.example.txt")
>
> #The file write.emusegs.example.txt would have been written to R_HOME
> ## Not run: unlink("write.emusegs.example.txt")
>
>
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 17.05 0.71 17.76 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-release-windows-x86_64
Version: 2.4.0
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:
4 aU 1131.690 1248.630 K67MR007
5 aI 1460.310 1650.440 K67MR007
6 aI 621.437 767.500 K67MR009
7 aU 1540.940 1685.690 K67MR009
8 OY 1914.810 2007.940 K67MR009
9 OY 1021.440 1142.440 K67MR011
10 aI 2206.560 2328.500 K67MR011
> ## Not run: write.emusegs(dip, "write.emusegs.example.txt")
>
> #The file write.emusegs.example.txt would have been written to R_HOME
> ## Not run: unlink("write.emusegs.example.txt")
>
>
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 16.37 0.88 17.27 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-x86_64