You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice how yarn run thing-serial correctly propagates exit 1 from thing:1. However, yarn run thing-parallel ignores both non-zero exit codes and succeeds.
Is there a way to propagate failures from background jobs in yarn? If not, what are the intended use-cases for this feature? The fact that they always succeed disqualifies them from many scenarios IMO (for example running multiple linters in parallel).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Yarn's portable shell supports running tasks in parallel with the
task &
syntax. This works great when tasks succeed:However, when the background jobs fail, the failures are ignored and yarn run succeeds anyway:
Notice how
yarn run thing-serial
correctly propagatesexit 1
fromthing:1
. However,yarn run thing-parallel
ignores both non-zero exit codes and succeeds.Is there a way to propagate failures from background jobs in yarn? If not, what are the intended use-cases for this feature? The fact that they always succeed disqualifies them from many scenarios IMO (for example running multiple linters in parallel).
Beta Was this translation helpful? Give feedback.
All reactions