Pls try agaibn, if it fails again, pls let me know privately.
Best,
Uwe Ligges
On 26.08.2020 15:13, Nicholas Tierney wrote:
Hi Uwe,
OK thank you for that, good to know! I imagine it might be a bit tricky
to know when, but do you have an idea of when submissions might return
to normal? Or should I be good to submit again soon?
Thanks again,
Nick
On Wed, 26 Aug 2020 at 23:06, Uwe Ligges
<lig...@statistik.tu-dortmund.de
<mailto:lig...@statistik.tu-dortmund.de>> wrote:
Friends, thias looks like a hang in the CRAN incoming feasibility
checks, hence may well be some web related issue as it seems it ran
into
the timeout there.
Best,
Uwe Ligges
On 26.08.2020 14:57, Nicholas Tierney wrote:
> Hi Michael,
>
> I do indeed have quite a few examples in the package, this hasn't
been a
> problem in the past, but I guess I could try reducing them down.
Have you
> had this problem before?
>
> Cheers,
>
> Nick
>
> On Wed, 26 Aug 2020 at 22:49, Michael Dewey
<li...@dewey.myzen.co.uk <mailto:li...@dewey.myzen.co.uk>> wrote:
>
>> Dear Nicholas
>>
>> Do you in fact have many examples in the package? Perhaps for some
>> mysterious reason they take longer there than when you check at
home.
>>
>> Michael
>>
>> On 25/08/2020 14:54, Nicholas Tierney wrote:
>>> Hi Everyone,
>>>
>>> I have an error when submitting to Winbuilder for my R package,
naniar
>>> <https://github.com/njtierney/naniar>.
>>>
>>> When using `devtools::check_win_devel()` or
>> `devtools::check_win_release()`
>>> on naniar, I get the following logfile from winbuilder:
>>>
>>> ```
>>> * using log directory
'd:/RCompile/CRANguest/R-release/naniar.Rcheck'
>>> * using R version 4.0.2 (2020-06-22)
>>> * using platform: x86_64-w64-mingw32 (64-bit)
>>> * using session charset: ISO8859-1
>>> * checking for file 'naniar/DESCRIPTION' ... OK
>>> * checking extension type ... Package
>>> * this is package 'naniar' version '0.5.3'
>>> * package encoding: UTF-8
>>> * checking CRAN incoming feasibility ... ERROR
>>> 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 ?)
>>> ========
>>> ```
>>>
>>> (submission URL here:
https://win-builder.r-project.org/77PYyM2kMri1/)
>>>
>>> I had previously thought this was a problem to do with CRAN
being closed
>>> last week, but apparently this is not the case, and it should
have been
>>> working. I cannot find any details on CRAN for this, but it
passes build
>> on
>>> R HUB for windows, and it passes build with no warnings,
errors, or notes
>>> for me on Mac OSX, as well as on github actions (windows,
macOS, and
>>> ubuntu).
>>>
>>> Just wondering if anyone has thoughts on this? I have also cross
>>> posted on Rstudio
>>> community
>>> <
>>>
>>
https://community.rstudio.com/t/winbuilder-error-check-process-probably-crashed-or-hung-up-for-20-minutes-killed/77492
>>>> ,
>>> in case that is of interest.
>>>
>>> Thanks for your time, and apologies if I have missed something
obvious.
>>>
>>> All the best,
>>>
>>> Nick
>>>
>>> [[alternative HTML version deleted]]
>>>
>>> ______________________________________________
>>> R-package-devel@r-project.org
<mailto:R-package-devel@r-project.org> mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>>>
>>
>> --
>> Michael
>> http://www.dewey.myzen.co.uk/home.html
>>
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> R-package-devel@r-project.org
<mailto:R-package-devel@r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
