Databases
StackOverflow2013
Postsdbo
POHow do I suppress the huge stack trace after a rake TestTask failure?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I suppress the huge stack trace after a rake TestTask failure?
    primarykey
    data
    text
    <p>I'm setting up a rakefile for a project, and I've defined some rake TestTasks. I ran a simple sanity test that does an <code>assert_equal(1, 2)</code> just to check the output, and, in addition to the usual failure output, I get this mess:</p> <pre><code>rake aborted! Command failed with status (1): [/usr/bin/ruby -w -I"lib:." "/usr/lib/ruby/...] /usr/lib/ruby/1.9.1/rake.rb:993:in `block in sh' /usr/lib/ruby/1.9.1/rake.rb:1008:in `call' /usr/lib/ruby/1.9.1/rake.rb:1008:in `sh' /usr/lib/ruby/1.9.1/rake.rb:1092:in `sh' /usr/lib/ruby/1.9.1/rake.rb:1027:in `ruby' /usr/lib/ruby/1.9.1/rake.rb:1092:in `ruby' /usr/lib/ruby/1.9.1/rake/testtask.rb:115:in `block (2 levels) in define' /usr/lib/ruby/1.9.1/rake.rb:1110:in `verbose' /usr/lib/ruby/1.9.1/rake/testtask.rb:100:in `block in define' /usr/lib/ruby/1.9.1/rake.rb:634:in `call' /usr/lib/ruby/1.9.1/rake.rb:634:in `block in execute' /usr/lib/ruby/1.9.1/rake.rb:629:in `each' /usr/lib/ruby/1.9.1/rake.rb:629:in `execute' /usr/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain' /usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize' /usr/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain' /usr/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites' /usr/lib/ruby/1.9.1/rake.rb:602:in `each' /usr/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites' /usr/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain' /usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize' /usr/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain' /usr/lib/ruby/1.9.1/rake.rb:581:in `invoke' /usr/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task' /usr/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level' /usr/lib/ruby/1.9.1/rake.rb:2019:in `each' /usr/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level' /usr/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling' /usr/lib/ruby/1.9.1/rake.rb:2013:in `top_level' /usr/lib/ruby/1.9.1/rake.rb:1992:in `run' /usr/bin/rake:31:in `&lt;main&gt;' </code></pre> <p>How do I get rid of it? I don't want to have to scroll up past 20 lines of junk to see my test failures.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USdecitrig
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow do I suppress the huge stack trace after a rake TestTask failure?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow do I suppress the huge stack trace after a rake TestTask failure?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow do I suppress the huge stack trace after a rake TestTask failure?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload