the order of task under deps is random

[sinlov]

Description

The order of task under deps is random. Most of the time, the running order will affect the execution result.

task --experiments                                 
* GENTLE_FORCE:     off
* REMOTE_TASKFILES: off
* MAP_VARIABLES:    off
* ENV_PRECEDENCE:   off

Version

3.41.0

Operating system

linux, windows, macOS

Experiments Enabled

No response

Example Taskfile

version: '3'
silent: true

tasks:
  a:
    desc: "task a"
    internal: true
    cmds:
      - echo "a"

  b:
    desc: "task b"
    internal: true
    cmds:
      - echo "b"

  c:
    desc: "task c"
    internal: true
    cmds:
      - echo "c"

  tests.deps.sequence:
    desc: show deps sequence
    deps:
      - task: a
      - task: b
      - task: c

[pd93]

As described in the docs, deps are always run in parallel by design. If you want to call tasks serially, you should use cmds instead:

version: 3

tasks:
  default:
    cmds:
      - task: a
      - task: b
      - task: c

[sinlov]

@pd93 Most executions require a dependency sequence, such as parse test coverage, which requires generate coverage first. If it is executed in a probabilistic order, it will lead to unstable and unreliable task execution.

If deps is used to reuse the existing task yaml, then deps will be completely inactive, and eventually lead to repeated writing cmds

Especially when combined with deps + vars to functionize the task (similar to the usage method of DSL), but currently the execution of deps is random, which ruins more possibilities of go-task.

It should be mentioned that the task oriented non-loop diagram design of makefile is very conducive to reuse. The most important design is that the task dependency is orderly and has anti-loop checking.