-
Notifications
You must be signed in to change notification settings - Fork 124
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
Only first of many parallel kernel stages is executed. #46
Labels
Comments
dkushner
changed the title
Skipping a single parallel kernel stage.
Only first of many parallel kernel stages is executed.
Jul 24, 2017
This is a bug....suspect it will be fixed in the dev branch, however, will add to queue for the mainline branch too. Is there any chance you could submit a test case for this one? Dropping code in the comment box or submitting a pull request to add the test case would be awesome. Thanks for finding!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a pipeline laid out something like this:
Where
videoSource
is a multi-port output,convertColor
andresize
are all 1-1 input-to-output setups that are clonable andvideoSink
is aparallel_k
fan-in stage.For some reason, when I run my application only
videoSource
,convertColor
andvideoSink
are run in this configuration. If I use onlyconvertColor
orresize
individually, they are each run but if I try to use any two together for the joined parallel kernel, only the first is run.Am I using the incorrect syntax or missing something else?
The text was updated successfully, but these errors were encountered: