Also using R-devel might help - the forking support in parallel has been
made more robust against race conditions, but the changes are probably
too substantial to port to 3.4.x. If you find how to cause a race
condition using parallel/forking in R-devel, a report would be greatly
appreciated.
Dear R-Devel List,
**TL;DR:** The function **parLapplyLB** of the parallel package has
[reportedly][1] (see also attached RRD output) not
been doing its job, i.e. not actually balancing the load. My colleague Dirk
Sarpe and I found the cause of the problem
and we also have a patch to fix it (att
Hi,
I fixed a minor typo in an error message from grDevices. Please see
attached for a patch to revision 74246.
Thanks,
John
Index: src/library/grDevices/src/colors.c
===
--- src/library/grDevices/src/colors.c (revision 74246)
+++
Hi all,
I'm trying to set up the Windows Rtools toolset for building packages
with compiled code. I installed for Windows R-3.4.3 from CRAN and
installed Rtools-3.4 in a custom location M:\R\R-3.4.3 and
M:\R\Rtools-3.4
Following the instructions, in shell, I set
Path=M:\R\Rtools-3.4\bin;M:\R\Rtoo
I can confirm the behaviour that you report.
Usually I put Rtools in c:\programs\Rtools and modify the path
accordingly. Recently (don't recall for how long) I have encountered
the same problems as you have and I have resorted to moving Rtools to
c:\Rtools
I have no idea as how to proceed; perha