(I am a maintainer of R packages in Macports, including R-crew. There is no claim from my side that issues below are necessarily a result of bugs in crew; it is possible that the set-up has some issues on our side. But an advice gonna be appreciated.)
Using crew 0.9.1 with R 4.3.3 and Macports build env.
There are two issues. The first one is with R-targets, but the log points specifically at crew:
── Failed tests ────────────────────────────────────────────────────────────────
Error ('test-tar_make.R:47:3'): tar_make() works with crew
<crew_error/crew/tar_condition_run/tar_condition_targets/rlang_error/error/condition>
Error: Error running targets::tar_make()
Error messages: targets::tar_meta(fields = error, complete_only = TRUE)
Debugging guide: https://books.ropensci.org/targets/debugging.html
How to ask for help: https://books.ropensci.org/targets/help.html
Last error message:
{crew} worker 1 launched 5 times in a row without completing any tasks. Either troubleshoot or raise launch_max above 5. Details: https://wlandau.github.io/crew/articles/risks.html#crashes
Last error traceback:
stop(x)
.handleSimpleError(function (condition) { state$error <- build_mess...
h(simpleError(msg, call))
Backtrace:
▆
1. └─targets::tar_make(...)
2. └─targets:::callr_outer(...)
3. ├─targets:::if_any(...)
4. └─targets:::callr_error(traced_condition = out, fun = fun)
5. └─targets::tar_throw_run(message, class = class(traced_condition$condition))
6. └─targets::tar_error(...)
7. └─rlang::abort(message = message, class = class, call = tar_empty_envir)
This is the only error in R-targets test suite I get ([ FAIL 1 | WARN 0 | SKIP 512 | PASS 2940 ]).
Having encountered this, I then ran crew own test suite, and got two errors (one in tests and one in vignettes):
Errors in running code in vignettes:
when running code in ‘groups.Rmd’
...
> group$start()
> group$push(name = "my task", command = sqrt(4), controller = "semi-persistent")
> group$wait(controllers = "semi-persistent")
When sourcing ‘groups.R’:
Error: {crew} worker 1 launched 5 times in a row without completing any tasks. Either troubleshoot or raise launch_max above 5. Details: https://wlandau.github.io/crew/articles/risks.html#crashes
Execution halted
when running code in ‘introduction.Rmd’
...
> task <- controller$pop()
> task
NULL
> controller$wait(mode = "all")
When sourcing ‘introduction.R’:
Error: {crew} worker 1 launched 5 times in a row without completing any tasks. Either troubleshoot or raise launch_max above 5. Details: https://wlandau.github.io/crew/articles/risks.html#crashes
Execution halted
when running code in ‘plugins.Rmd’
...
> controller$start()
> controller$push(name = "get worker IP address and process ID",
+ command = paste(getip::getip(type = "local"), ps::ps_pid()))
> controller$wait()
When sourcing ‘plugins.R’:
Error: {crew} worker 1 launched 5 times in a row without completing any tasks. Either troubleshoot or raise launch_max above 5. Details: https://wlandau.github.io/crew/articles/risks.html#crashes
Execution halted
(I am a maintainer of
Rpackages in Macports, includingR-crew. There is no claim from my side that issues below are necessarily a result of bugs increw; it is possible that the set-up has some issues on our side. But an advice gonna be appreciated.)Using
crew0.9.1 withR4.3.3 and Macports build env.There are two issues. The first one is with
R-targets, but the log points specifically atcrew:This is the only error in
R-targetstest suite I get ([ FAIL 1 | WARN 0 | SKIP 512 | PASS 2940 ]).Having encountered this, I then ran
crewown test suite, and got two errors (one in tests and one in vignettes):Overall test results appear acceptable: [ FAIL 1 | WARN 0 | SKIP 85 | PASS 218 ].
@wlandau Could you suggest what may be causing this?