Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parallelization not supported on Windows #46

Closed
wleoncio opened this issue Jun 26, 2024 · 0 comments · Fixed by #55
Closed

Parallelization not supported on Windows #46

wleoncio opened this issue Jun 26, 2024 · 0 comments · Fixed by #55
Assignees
Labels
bug Something isn't working

Comments

@wleoncio
Copy link
Member

wleoncio commented Jun 26, 2024

Running test-parallel.R on a Windows machine gives the following error:

── Error ('test-parallel.R:78:3'): (code run outside of `test_that()`) ─────────
Error in `makeForkCluster(nnodes = spec, ...)`: fork clusters are not supported on Windows
Backtrace:1. └─MADMMplasso (local) mad_wrap(legacy = TRUE, parallel = TRUE, pal = FALSE) at test-parallel.R:92:1
 2.   ├─base::suppressMessages(...) at test-parallel.R:78:3
 3.   │ └─base::withCallingHandlers(...)
 4.   └─MADMMplasso::MADMMplasso(...)
 5.     └─parallel::makeCluster(cl1, type = "FORK") at MADMMplasso/R/MADMMplasso.R:210:5
 6.       └─parallel::makeForkCluster(nnodes = spec, ...)

A couple possible solutions

  1. Dropping support for parallel = TRUE on Windows
  2. Finding an alternative to fork clusters on Windows
@wleoncio wleoncio added the bug Something isn't working label Jun 26, 2024
wleoncio added a commit that referenced this issue Aug 20, 2024
Not as elegant as simply using `makeCluster()`, but this avoids rewriting some unit tests. May be improved in the future.
@wleoncio wleoncio linked a pull request Aug 20, 2024 that will close this issue
@wleoncio wleoncio self-assigned this Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant