Closed HenrikBengtsson closed 6 years ago
I believe the same underlying problem is also hitting future.batchtools, cf. https://cran.r-project.org/web/checks/check_results_future.batchtools.html
CRAN errors are going away again. Fixed in rev 73867: https://github.com/wch/r-source/commit/b851fdaa1b80c19607f4641be440c48965ceab80
Issue
On the most recent version of R-devel:
Note how those
tryCatch()
calls keeps picking up the previously generated error and not the warning produced by the future as we'd expect/get in R 3.4.3 (and all other versions of R tested):This was caught by CRAN checks on R-devel, cf. https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-gcc/future-00check.html.
Troubleshooing
I suspect this is related to R-devel SVN commit 73853 ("Preserve the error buffer when an on.exit action is processed while jumping to a calling handler. Resolves an issue reported by Bill Dunlap.") on 2017-12-06. See https://github.com/wch/r-source/commit/5f86e82f26f7066d25732ca11b48bd95ef95e63c for diff.
Futures uses
on.exit()
internally.Action
I'll give it a few days before I report to R-devel / Luke T.