Hello List! I am prepping gtsummary for a new release, but I am running into a problem with the CRAN win-builder. The package is passing checks on my local Windows machine, another local Windows machine, on a GitHub Actions Windows machine ( https://github.com/ddsjoberg/gtsummary/runs/729569705?check_suite_focus=true). However I am getting this error on win-builder in `00check.log`: 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 ?) ======== link to win-builder results https://win-builder.r-project.org/SFSFeP44df58/ Any ideas on how to troubleshoot this error? The build is also passing on macOS and Ubuntu GitHub Actions checks. Thank you! Daniel
[R-pkg-devel] win-builder failing without informative message
5 messages · Ben Bolker, Gábor Csárdi, Uwe Ligges +1 more
In my opinion, if you've tested on multiple Windows system that you've done your due diligence and shouldn't worry too much about win-builder hiccups ... On Tue, Jun 2, 2020 at 10:09 AM Daniel Sjoberg
<danield.sjoberg at gmail.com> wrote:
Hello List! I am prepping gtsummary for a new release, but I am running into a problem with the CRAN win-builder. The package is passing checks on my local Windows machine, another local Windows machine, on a GitHub Actions Windows machine ( https://github.com/ddsjoberg/gtsummary/runs/729569705?check_suite_focus=true). However I am getting this error on win-builder in `00check.log`: 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 ?) ======== link to win-builder results https://win-builder.r-project.org/SFSFeP44df58/ Any ideas on how to troubleshoot this error? The build is also passing on macOS and Ubuntu GitHub Actions checks. Thank you! Daniel [[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Seems like your tests did not finish: https://win-builder.r-project.org/SFSFeP44df58/examples_and_tests/tests_x64/testthat.Rout Either they take too long, or they froze. You can use a different testthat reporter, to see which one is stuck, e.g. like this: https://github.com/cran/desc/blob/3e52b4923c7852bc00fbc94887c42657ffc67283/tests/testthat.R#L4 Gabor
On Tue, Jun 2, 2020 at 3:09 PM Daniel Sjoberg <danield.sjoberg at gmail.com> wrote:
Hello List! I am prepping gtsummary for a new release, but I am running into a problem with the CRAN win-builder. The package is passing checks on my local Windows machine, another local Windows machine, on a GitHub Actions Windows machine ( https://github.com/ddsjoberg/gtsummary/runs/729569705?check_suite_focus=true). However I am getting this error on win-builder in `00check.log`: 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 ?) ======== link to win-builder results https://win-builder.r-project.org/SFSFeP44df58/ Any ideas on how to troubleshoot this error? The build is also passing on macOS and Ubuntu GitHub Actions checks. Thank you! Daniel [[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Simply: ** running tests for arch 'i386' ... [14m] OK And the CRAN threshold for the whole package is 10 min. So only the tests for two architectures already take ~ 30 min here. which is too much for CRAN. Best, Uwe Ligges
On 02.06.2020 16:13, G?bor Cs?rdi wrote:
Seems like your tests did not finish: https://win-builder.r-project.org/SFSFeP44df58/examples_and_tests/tests_x64/testthat.Rout Either they take too long, or they froze. You can use a different testthat reporter, to see which one is stuck, e.g. like this: https://github.com/cran/desc/blob/3e52b4923c7852bc00fbc94887c42657ffc67283/tests/testthat.R#L4 Gabor On Tue, Jun 2, 2020 at 3:09 PM Daniel Sjoberg <danield.sjoberg at gmail.com> wrote:
Hello List! I am prepping gtsummary for a new release, but I am running into a problem with the CRAN win-builder. The package is passing checks on my local Windows machine, another local Windows machine, on a GitHub Actions Windows machine ( https://github.com/ddsjoberg/gtsummary/runs/729569705?check_suite_focus=true). However I am getting this error on win-builder in `00check.log`: 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 ?) ======== link to win-builder results https://win-builder.r-project.org/SFSFeP44df58/ Any ideas on how to troubleshoot this error? The build is also passing on macOS and Ubuntu GitHub Actions checks. Thank you! Daniel [[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Thank you! I added skip on CRAN to the time intensive tests, and it's passing again. MUCH APPRECIATED! On Tue, Jun 2, 2020 at 12:03 PM Uwe Ligges <ligges at statistik.tu-dortmund.de> wrote:
Simply: ** running tests for arch 'i386' ... [14m] OK And the CRAN threshold for the whole package is 10 min. So only the tests for two architectures already take ~ 30 min here. which is too much for CRAN. Best, Uwe Ligges On 02.06.2020 16:13, G?bor Cs?rdi wrote:
Seems like your tests did not finish:
Either they take too long, or they froze. You can use a different testthat reporter, to see which one is stuck, e.g. like this:
Gabor On Tue, Jun 2, 2020 at 3:09 PM Daniel Sjoberg <danield.sjoberg at gmail.com>
wrote:
Hello List! I am prepping gtsummary for a new release, but I am running into a
problem
with the CRAN win-builder. The package is passing checks on my local Windows machine, another local Windows machine, on a GitHub Actions Windows machine (
However I am getting this error on win-builder in `00check.log`: 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 ?)
========
link to win-builder results
Any ideas on how to troubleshoot this error? The build is also passing
on
macOS and Ubuntu GitHub Actions checks.
Thank you!
Daniel
[[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel