-
Notifications
You must be signed in to change notification settings - Fork 3
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
Pip 1537 nested scatter #36
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small comments. I think this PR would greatly benefit from tests too. You mentioned "a test toy problem with complex subworkflows", could you add it here? I don't think we need CircleCI right now but at the minimum adding tests with pytest would be good.
@paul-sud: I added pytests to test subworkflows and nested scatters. I will make a new ticket/PR for CircleCI and more refactoring. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks OK, but we might want to consider storing the metadata JSONs for the tests instead of creating them every time. Then tests will run much faster and test fixtures will be simpler. You could still keep the WDL around in case you need to recreate them.
@paul-sud Yep, fixed as you suggested. |
Hot fix for nested scatters.
There is no circleci testing for croo yet.
Tested with atac, chip, hic and some toy WDLs with subworkflows and nested scatters.