Displaying 6 results from an estimated 6 matches for "elapsedlimitvalu".
Did you mean:
elapsedlimitvalue
2016 Oct 26
3
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
...); - which is Windows specific and
could be another important difference between Windows and Unix. This
function is defined in:
* src/main/errors.c
(https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134)
The do_setTimeLimit() function controls global variables cpuLimitValue
and elapsedLimitValue, which are checked in R_ProcessEvents(), but
other than setting the timeout limits I don't think it's involved in
the runtime checks. The do_setTimeLimit() is defined in:
* src/main/sysutils.c
(https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L1736)
Unfortunately, ri...
2016 Oct 27
2
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
...nce between Windows and Unix. This
>> function is defined in:
>>
>> * src/main/errors.c
>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134)
>>
>>
>> The do_setTimeLimit() function controls global variables cpuLimitValue
>> and elapsedLimitValue, which are checked in R_ProcessEvents(), but
>> other than setting the timeout limits I don't think it's involved in
>> the runtime checks. The do_setTimeLimit() is defined in:
>>
>> * src/main/sysutils.c
>> (https://github.com/wch/r-source/blob/trunk/src/main...
2016 Oct 26
0
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
...be another important difference between Windows and Unix. This
> function is defined in:
>
> * src/main/errors.c
> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134)
>
>
> The do_setTimeLimit() function controls global variables cpuLimitValue
> and elapsedLimitValue, which are checked in R_ProcessEvents(), but
> other than setting the timeout limits I don't think it's involved in
> the runtime checks. The do_setTimeLimit() is defined in:
>
> * src/main/sysutils.c
> (https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L...
2016 Oct 31
1
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
...defined in:
>>>>
>>>> * src/main/errors.c
>>>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134)
>>>>
>>>>
>>>> The do_setTimeLimit() function controls global variables cpuLimitValue
>>>> and elapsedLimitValue, which are checked in R_ProcessEvents(), but
>>>> other than setting the timeout limits I don't think it's involved in
>>>> the runtime checks. The do_setTimeLimit() is defined in:
>>>>
>>>> * src/main/sysutils.c
>>>>
>>>...
2016 Oct 31
0
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
...his
>>> function is defined in:
>>>
>>> * src/main/errors.c
>>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134)
>>>
>>>
>>> The do_setTimeLimit() function controls global variables cpuLimitValue
>>> and elapsedLimitValue, which are checked in R_ProcessEvents(), but
>>> other than setting the timeout limits I don't think it's involved in
>>> the runtime checks. The do_setTimeLimit() is defined in:
>>>
>>> * src/main/sysutils.c
>>>
>>> (https://github.com...
2016 Oct 26
5
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
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 immediately and causes an interrupt after ~1 second;
> system.time({ Sys.sleep(10);