Oops, didn’t check the recent messages :) @Watson/Mark: I will remove that `or true` part, but let’s wait with upgrading rake until after 0.11, unless Laurent gives the go ahead.
On Oct 5, 2011, at 9:29 AM, Josh Abernathy wrote: > Thanks, filed: https://www.macruby.org/trac/ticket/1399 > > > On Oct 5, 2011, at 12:20 AM, Eloy Durán wrote: > >> Nope, you’re not missing anything, that’s a bug. Please file a ticket for it. >> >> >> On Oct 2, 2011, at 2:45 AM, Josh Abernathy wrote: >> >>> I wanted to verify that I'm not crazy and I'm not doing something stupid >>> before I create a ticket for this. >>> >>> The `rake` that comes with MacRuby (both 0.10 and the nightly) seems to >>> always print a full trace when a task raises an exception. For example, if >>> I run: >>> >>> task :blah do >>> raise Exception, 'whatev' >>> end >>> >>> With MacRuby, I get: >>> >>> rake aborted! >>> whatev >>> /Volumes/GitHub/Mac/blah/rakefile:2:in `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:632:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:629:in >>> `execute' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:595:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/monitor.rb:201:in >>> `synchronize' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:588:in >>> `invoke_with_call_chain' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:581:in >>> `invoke' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2042:in >>> `invoke_task' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2059:in >>> `standard_exception_handling' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2014:in >>> `top_level' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:1993:in >>> `run' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/bin/macrake:31:in >>> `<main>' >>> >>> If I run with Ruby 1.9.2, I get: >>> >>> rake aborted! >>> whatev >>> >>> Tasks: TOP => blah >>> (See full trace by running task with —trace) >>> >>> And if I use Ruby 1.9.2 and run `rake` with —trace, I get an output like >>> that of MacRuby. So MacRuby seems to *always* print the full trace, >>> regardless of whether I include the —trace flag. This is pretty annoying >>> when running tests because of the constant visual noise when I get a failed >>> test. >>> >>> Am I missing something? Is there any way to suppress the trace? >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
