Skip to content
Prev 933 / 12125 Next

[R-pkg-devel] Warning that are Unintentionally OS-Specific (Maybe Bug in warning?)

Digging into the code (specifically by setting
options(warn=2,error=recover), I see that the warning is happening
during this call:

    tmp.results <- parallel::mclapply(X = conc.dose, FUN =
pk.nca.intervals,
    intervals = data$intervals, options = data$options)

Since mclapply "relies on forking and hence is not available on Windows
unless ?mc.cores = 1?" (from ?mclapply), I can imagine that it's *not*
actually being run in parallel on Windows.  It also wouldn't surprise me
at all if it took a little bit of care to make sure that warnings were
correctly passed back from code chunks run in parallel.

  This StackOverflow post seems to ask the same question as yours:

http://stackoverflow.com/questions/21486658/warnings-suppressed-with-mclapply-in-r

  based on the discussion there, it seems as though it might be worth
bringing this up on r-devel/submitting a bug report ...

   Ben Bolker
On 16-07-20 03:13 PM, Bill Denney wrote: