-
Notifications
You must be signed in to change notification settings - Fork 326
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
Hang in state_rebuilder for mid-execution capture of SaschaWillems pipelines example #2390
Comments
bjoeris
added a commit
to bjoeris/gapid
that referenced
this issue
Nov 23, 2018
The problematic case is a state containing multiple pipelines, some of which have 0 basePipeline, and some of which have a basePipeline that forms a loop or doesn't exist. This caused both `numHandled` and `len(unhandledPipelines)` to be non-zero forever. This change resets `numHandled` for each pass over `unhandledPipelines`. Fixes google#2390
The immediate symptom of the hang is fixed in #2391, but this leaves open the problem of loops in the |
bjoeris
added a commit
to bjoeris/gapid
that referenced
this issue
Nov 23, 2018
The problematic case is a state containing multiple pipelines, some of which have 0 basePipeline, and some of which have a basePipeline that forms a loop or doesn't exist. This caused both `numHandled` and `len(unhandledPipelines)` to be non-zero forever. This change resets `numHandled` for each pass over `unhandledPipelines`. Fixes google#2390
bjoeris
added a commit
to bjoeris/gapid
that referenced
this issue
Nov 24, 2018
The problematic case is a state containing multiple pipelines, some of which have 0 basePipeline, and some of which have a basePipeline that forms a loop or doesn't exist. This caused both `numHandled` and `len(unhandledPipelines)` to be non-zero forever. This change resets `numHandled` for each pass over `unhandledPipelines`. Fixes google#2390
bjoeris
added a commit
that referenced
this issue
Nov 26, 2018
The problematic case is a state containing multiple pipelines, some of which have 0 basePipeline, and some of which have a basePipeline that forms a loop or doesn't exist. This caused both `numHandled` and `len(unhandledPipelines)` to be non-zero forever. This change resets `numHandled` for each pass over `unhandledPipelines`. Fixes #2390
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is an infinite loop in
getPipelinesInOrder
The text was updated successfully, but these errors were encountered: