Skip to content

Conversation

jdblischak
Copy link
Contributor

Closes #87

The macOS-specific problem was fixed in {parallelly 1.45.1}, which was accepted on CRAN on 2025-07-24

This PR removes the troubleshooting jobs and adds a macOS job that tests against the branch "develop" of {parallelly} for early detection of similar problems going forward

xref: Merck/simtrial#337, futureverse/parallelly@b26aef3

@jdblischak
Copy link
Contributor Author

@HenrikBengtsson please review. This is a minor follow-up to #88

@HenrikBengtsson
Copy link
Collaborator

@HenrikBengtsson please review. This is a minor follow-up to #88

Not sure what to look at, but parallelly 1.45.1 [2025-07-24] is on CRAN and should have the resolved the original issue.

@jdblischak
Copy link
Contributor Author

Agreed. The original issue has been resolved. Much appreciated!

This PR updates the GitHub workflow so that {doFuture} is regularly tested against the branch "develop" of the {parallelly} repository. The idea is to catch these sorts of potential problems earlier.

@HenrikBengtsson
Copy link
Collaborator

I see. Yes, that SGTM.

@jdblischak
Copy link
Contributor Author

I see. Yes, that SGTM.

Great! I don't have write-access to this repository. If you are happy with the changes to the workflow, please merge this PR. Thanks!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

{doFuture} appears to be incompatible with {parallelly} 1.45.0 in macOS GitHub Actions jobs

2 participants