Search Results

Search found 2 results on 1 pages for 'martinos'.

Page 1/1 | 1 

  • How can I make Ruby rake display the full backtrace on uncaught exception

    - by Martinos
    As you may know rake swallows the full backtrace on uncaught exception. If I want to have a full backtrace, I need to add the --trace option. I find this very annoying because some of my tasks take long time to run (up to 6 hours), when it crashes I don't have any debugging info. I need to run it again with the --trace. On top of that, the system may not be in the same state as when the error occurred, so it may not show afterward. I always have to add --trace on any tasks. This displasy stuff that I don't want to see when the task is executed. Is there a way to change this default behaviour? (which I don't think is useful at all)

    Read the article

1