Open nemonemi opened 11 months ago
Hi there @nemonemi ! Thanks for filing an issue! Can you please provide a minimum reproduction repository? This will help us understand the issue better and solve it quicker! Thanks!
Hey, @mandarini, thanks for the quick response. Unfortunately, I have no idea regarding the cause, and because it's not constant, although it happens often, I wouldn't know where to start to simulate it, and I cannot share the project where it is happening.
This can happen if the process is killed (e.g. by OOM killer) and unfortunately Nx doesn't show the exit code of tasks, it just swallows them all and then itself exits with 1. I'd love a way to have Nx log the exit code of failed tasks.
This issue has been automatically marked as stale because it hasn't had any activity for 6 months. Many things may have changed within this time. The issue may have already been fixed or it may not be relevant anymore. If at this point, this is still an issue, please respond with updated information. It will be closed in 21 days if no further activity occurs. Thanks for being a part of the Nx community! 🙏
Current Behavior
Randomly, a build fails, and after re-running it passes after a random number of tries. A build failing wouldn't be a problem, but it not showing the reason is!
Here is the full output with both
--verbose
and--output-style=stream
applied.Expected Behavior
A failing build, as all other actions like e2e, unit tests, or linting should report the reason for failing.
GitHub Repo
No response
Steps to Reproduce
Unable to produce a repo because it is not clear as to why it is happening.
Nx Report
Failure Logs