On 26.09.2014 18:48, Jeff Forcier wrote:
Yup, just turn on 'debug' output in whichever way is most convenient
for you:
http://docs.fabfile.org/en/1.10/usage/output_controls.html#hiding-and-or-showing-output-levels
E.g. `fab --show=debug <tasks>`
On our servers several hundred tasks get executed on one day.
Sometimes (less then 99.9%) there is an unusual error and the scripts aborts.
The current error message does not help us: We want a stacktrace.
Running the task again does to reproduce the error. It works.
How to debug something like this?
If we turn on --show=debug on our production servers, the logs get unreadable
since
there is way too much output.
Can you understand what makes me unhappy?
It would be very nice to see stacktraces without running fabric in debug mode.
Thomas Güttler
--
Thomas Güttler
http://thomas-guettler.de/
_______________________________________________
Fab-user mailing list
Fab-user@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fab-user
