Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

https://github.com/jenseng/turbo-parallel-continue-bug

Which canary version will you have in your reproduction?

turbo@2.4.3-canary.3

Enviroment information

turbo 2.4.3-canary.3

CLI:
   Version: 2.4.3-canary.3
   Path to executable: path/to/turbo-parallel-continue-bug/node_modules/turbo-darwin-arm64/bin/turbo
   Daemon status: Running
   Package manager: npm

Platform:
   Architecture: aarch64
   Operating system: macos
   WSL: false
   Available memory (MB): 3239
   Available CPU cores: 12

Environment:
   CI: None
   Terminal (TERM): xterm-256color
   Terminal program (TERM_PROGRAM): iTerm.app
   Terminal program version (TERM_PROGRAM_VERSION): 3.5.11
   Shell (SHELL): /bin/zsh
   stdin: false

Expected behavior

Specifying the --parallel flag should automatically set --continue to true, as documented here.

Actual behavior

Specifying the --parallel flag causes turbo to run with the (default) --continue=false behavior. If any task fails, then no more tasks will be run.

In order to ensure all tasks run, you need to explicitly set --continue.

To Reproduce

• Check out this repo
• Run npm install
• Run npx turbo run build --concurrency 2 --parallel
• Note that only 2 of the 5 tasks run (all build scripts intentionally fail)

Additional context

If the current behavior is desirable, this could just be treated as a documentation issue instead of a bug. IMO though implicitly setting --continue when using --parallel is likely what people expect to happen.