Re: [R-pkg-devel] R CMD Check: Tests running infinite

2017-02-07 Thread Gábor Csárdi
On Tue, Feb 7, 2017 at 8:16 PM, Henrik Bengtsson wrote: [...] > > So, to me it's not clear how this could make a difference in Patrick > case. By disabling this, i.e. Sys.setenv(R_TESTS=""), I don't see > how it affects running parallel+foreach+doParallel. Maybe

Re: [R-pkg-devel] R CMD Check: Tests running infinite

2017-02-07 Thread Gábor Csárdi
On Tue, Feb 7, 2017 at 8:16 PM, Henrik Bengtsson wrote: [...] > I wonder if those are mostly there because of cut'n'paste behavior. > I don't know. What I know is that I have seen it in about 5 of my packages, and I have also helped about 5 people that were stumbled

Re: [R-pkg-devel] R CMD Check: Tests running infinite

2017-02-07 Thread Hadley Wickham
>> A lot of packages have to work around this: >> https://github.com/search?q=user%3Acran+R_TESTS=Code > > I wonder if those are mostly there because of cut'n'paste behavior. It's not something I've ever advocated; I didn't realise there were so many people unsetting it. (devtools does it for

Re: [R-pkg-devel] R CMD Check: Tests running infinite

2017-02-07 Thread Henrik Bengtsson
On Mon, Feb 6, 2017 at 12:41 AM, Gábor Csárdi wrote: > I don't think it is specific for testthat. R CMD check sets R_TESTS when it > runs the tests, so the separate R process it starts can have some special > startup options. > > The problem happens if you start another R