Skip to content

Something seems to be unreasonable with example3 #8

Description

@haik

The output of example3 is:

ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_3
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_3
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_3
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
SUCCESS All children succeeded in finish_counts

Before moving on to count2, it will re-start count1. But why should it?
I don’t really understand it. I was wondering if anyone can help me?

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions