On Mon, Oct 31, 2016 at 9:36 AM, wrote:
> On Mon, 31 Oct 2016, Henrik Bengtsson wrote:
>
>> Thank you for looking into this Luke.
>>
>> On Thu, Oct 27, 2016 at 9:26 AM, wrote:
>>>
>>> On unix, unless event polling is enabled Sys.sleep just waits
On Mon, 31 Oct 2016, Henrik Bengtsson wrote:
Thank you for looking into this Luke.
On Thu, Oct 27, 2016 at 9:26 AM, wrote:
On unix, unless event polling is enabled Sys.sleep just waits in a
select() call (with a SIGINT handler in place) so the elapsed time
isn't
Thank you for looking into this Luke.
On Thu, Oct 27, 2016 at 9:26 AM, wrote:
> On unix, unless event polling is enabled Sys.sleep just waits in a
> select() call (with a SIGINT handler in place) so the elapsed time
> isn't checked until after the select call is
On unix, unless event polling is enabled Sys.sleep just waits in a
select() call (with a SIGINT handler in place) so the elapsed time
isn't checked until after the select call is complete. Rstudio uses
event polling, and in particular sets R_wait_usec to 1, which
means event and interrupt
Spencer also had tools and rsconnect loaded (via a namespace) but it doesn't
seem to make a difference for me if I load them. It also doesn't seem to matter
for me whether it is CRAN R, locally built R, Terminal, R.app. However, RStudio
differs
> setTimeLimit(elapsed=1)
Error: reached elapsed
> On 26 Oct 2016, at 04:44, Henrik Bengtsson wrote:
> ...
> This looks like a bug to me. Can anyone on macOS confirm whether this
> is also a problem there or not?
>
Tried it on macOS El Capitan and got this (running in R.app with R version
3.3.2 RC
On 26 Oct 2016, at 04:44 , Henrik Bengtsson wrote:
> This looks like a bug to me. Can anyone on macOS confirm whether this
> is also a problem there or not?
I don't know whether it is a problem ( ;-) ), but it does the same thing
(checked Mavericks, Yosemite and
> Spencer Graves
> on Tue, 25 Oct 2016 22:02:29 -0500 writes:
> On 10/25/2016 9:44 PM, Henrik Bengtsson wrote:
>> setTimeLimit(elapsed=1) causes a timeout error whenever a call takes
>> more than one second. For instance, this is how it works
On 10/25/2016 9:44 PM, Henrik Bengtsson wrote:
setTimeLimit(elapsed=1) causes a timeout error whenever a call takes
more than one second. For instance, this is how it works on Windows
(R 3.3.1):
setTimeLimit(elapsed=1)
Sys.sleep(10); message("done")
Error in Sys.sleep(10) : reached elapsed
setTimeLimit(elapsed=1) causes a timeout error whenever a call takes
more than one second. For instance, this is how it works on Windows
(R 3.3.1):
> setTimeLimit(elapsed=1)
> Sys.sleep(10); message("done")
Error in Sys.sleep(10) : reached elapsed time limit
Also, the error propagates
10 matches
Mail list logo