Update parallelism
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- r
- Domain
- testing-qa
Research direction
Review test-parallel-psock.R at lines 22 and 47 and test-parallel-seeds.R at lines 22 and 26, then consult ?tune::parallelism() as the issue suggests. Run the affected parallel tests and consider the work done when the listed deprecation warnings no longer appear.
Written by the indexing model from the issue text.
Description
In the spirit of #124, let's act on our own deprecation warnings 🧹
4. LDA parallel test ('test-parallel-psock.R:22:3') - ! tune detected a parallel backend registered with foreach but no backend registered with future.
i Support for parallel processing with foreach was soft-deprecated in tune 1.2.1.
i See ?parallelism (`?tune::parallelism()`) to learn more.
5. recipe-adjacent parallel test ('test-parallel-psock.R:47:3') - ! tune detected a parallel backend registered with foreach but no backend registered with future.
i Support for parallel processing with foreach was soft-deprecated in tune 1.2.1.
i See ?parallelism (`?tune::parallelism()`) to learn more.
6. parallel seeds ('test-parallel-seeds.R:22:3') - ! tune detected a parallel backend registered with foreach but no backend registered with future.
i Support for parallel processing with foreach was soft-deprecated in tune 1.2.1.
i See ?parallelism (`?tune::parallelism()`) to learn more.
7. parallel seeds ('test-parallel-seeds.R:26:3') - ! tune detected a parallel backend registered with foreach but no backend registered with future.
i Support for parallel processing with foreach was soft-deprecated in tune 1.2.1.
i See ?parallelism (`?tune::parallelism()`) to learn more.
- Dominant language
- R
- Stars
- 23
- Forks
- 0
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tidymodels/extratests
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
tidymodels/extratests#303 ·
-
upkeep
Difficulty 4/5 3-5 days Newbie friendliness 25/100
tidymodels/extratests#270 ·
-
bug upkeep
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tidymodels/extratests#254 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
tidymodels/extratests#253 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
tidymodels/extratests#252 ·
All issues in tidymodels/extratests
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
tidymodels/orbital#192 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mitchelloharawild/ggtime#39 ·
-
enhancement good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100