First attempt for issue https://github.com/pantsbuild/pants/issues/326
Review Request #655 - Created July 9, 2014 and submitted
|benjyw, ity, jsirois, stuhood, tejal|
First attempt for issue https://github.com/pantsbuild/pants/issues/326 End pants users arguably see no values from the stack trace (even if they occasionally do, they can use the reporting server log); but in PANTS_DEV mode, pants dev should see the stack. The change is to introduce a command line arg that pants bash script will pass to pants_exe if PANTS_DEV is set. And in pants_exe we setup an unhandled exception hook to print out the exception's stacktrace plus msg based on the cmdline arg's presence.
17:04:04 05:01 [specs] Waiting for background workers to finish. SUCCESS $ ./pants goal test tests::
This seems like a fine start, I just have 2 issues: 1 seems to me this must break parsing 2 in the long run it would be great to always have the backtrace available (perhaps in a log file) and just use the print flag to tee that info to stdout/stderr. I want to run down 1, 2 could be satisfied by a TODO/issue to track.
Please rebase again or pull master: $ git apply <(curl -sS https://rbcommons.com/s/twitter/r/655/diff/raw/) error: patch failed: src/python/pants/bin/pants_exe.py:31 error: src/python/pants/bin/pants_exe.py: patch does not apply Benjy has been busy.
Review request changed
merge from main repo: github.com:pantsbuild/pants.git
Revision 4 (+5613 -3357)