open-cli-tools / open-cli-tools/concurrently
Show stderr output from failing task
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.9k
- Forks
- 281
- Avg merge
- 17h 12m
- Merged PRs (30d)
- 1
Description
I'm using concurrently for a CI job on VSTS to run a bunch of tasks in parallel and fail fast if one does.
{
"scripts": {
"verify": "concurrently \"npm run build\" \"npm run lint\" \"npm run lint\" --kill-others-on-fail"
}
}
If the task fails, npm just logs the root-level "concurrently failed!" without any info on which one. Not very useful for CI logs.
What would be useful is, if a task fails, concurrently were to print its output (either stderr+stdout or just stederr).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the concurrently CLI entry point and trace how a child-task failure becomes the root-level failure message. Define done as identifying the failed task and showing its stderr, stdout, or both in CI output, then verify the behavior with the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100