-
Notifications
You must be signed in to change notification settings - Fork 54
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
The program has bug when the steps in a stage are set to concurrent #12
Comments
Hey there. Could you please provide me an example code for the buggy behaviour ? |
When I run the sample code you gave, the sample code is pipeline/examples/advanced/main.go The sample code creates a pipeline with three stages. The first stage is executed sequentially, the second and third stages are executed concurrently, and the first step of the third stage returns an error. I found that the first stage executed sequentially worked well, while the second and third stages executed concurrently failed, running the last step three times in both cases. The result is as follows,You can find that stage1 and stage2 both run step2, and run it three times.
Looking at the source code, I found that the stage.run() function uses closure functions, which I guess is where the bug came from.
|
Have you solved it? |
When I set up concurrent execution for the steps of a stage, I find that program always execute the last step.
Looking at the source code, I found closure functions used for concurrent execution, which I guess is where the bug came from.
The text was updated successfully, but these errors were encountered: