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

Caching options for clustermq_staged parallelism #533

Merged
merged 2 commits into from
Oct 6, 2018
Merged

Caching options for clustermq_staged parallelism #533

merged 2 commits into from
Oct 6, 2018

Conversation

wlandau
Copy link
Member

@wlandau wlandau commented Oct 6, 2018

Summary

Same as #532, but for parallelism = "clustermq_staged"

Related GitHub issues and pull requests

Checklist

  • I have read drake's code of conduct, and I agree to follow its rules.
  • I have read the guidelines for contributing.
  • I have listed any substantial changes in the development news.
  • I have added testthat unit tests to tests/testthat to confirm that any new features or functionality work correctly.
  • I have tested this pull request locally with devtools::check()
  • This pull request is ready for review.
  • I think this pull request is ready to merge.

@codecov-io
Copy link

codecov-io commented Oct 6, 2018

Codecov Report

Merging #533 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #533   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          71     71           
  Lines        6421   6440   +19     
=====================================
+ Hits         6421   6440   +19
Impacted Files Coverage Δ
R/config.R 100% <ø> (ø) ⬆️
R/clustermq.R 100% <100%> (ø) ⬆️
R/staged.R 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d6be094...057d32e. Read the comment docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants