Show stderr output from failing task #134
Labels
Comments
rekmarks
added a commit
to MetaMask/metamask-extension
that referenced
this issue
Oct 6, 2021
This PR fixes our local unit test package scripts. When the state migration unit tests were migrated to Jest in #12106, it left the `test:unit` script in a broken state, because it didn't tell `mocha` to ignore the state migration tests. Arguably, that script was already broken, since the most reasonably expectation from its name is that it runs _all_ unit tests. The PR makes it so that it does just that, by means of `concurrently`. Unfortunately, `concurrently` only outputs errors from child processes once (at the time when they exit, open-cli-tools/concurrently#134). This means that we have to search/navigate the output for this combined script to identify the failure. That said, it's better than the status quo.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using
concurrentlyfor 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,
concurrentlywere to print its output (either stderr+stdout or just stederr).The text was updated successfully, but these errors were encountered: