Replies: 1 comment 1 reply
-
It sounds to me like the behavior of the graph is correct, but possible that the amount of tasks being reported isn't. It's a little hard to say without a reproduction. Would you be able to open an Issue with a reproduction so we can take a look? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
I'm not sure if this is a misconfiguration, or a bug with turbo. The general setup is I have a repo with 14 packages, each with a "foo" script.
When I run
turbo foo
, I getTasks: 14 successful, 14 total
Two packages have an additional "bar" script. When bar has no
dependsOn
, I can runturbo bar
and getTasks: 2 successful, 2 total
But when "bar" depends "foo" being run in the same package, running
turbo bar
results inTasks: 16 successful, 16 total
.It runs
foo
in all 14 packages rather than the two packages that is necessary. Is it possible for turbo to only runfoo
for the two packages which need to runbar
?Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions