I recently reinstalled my gems for autotest, and since then I have
unintelligible output coming from autotest like this (note everything
after unit_diff -u)
loading autotest/rails
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
-I.:lib:test -rubygems -e “%w[test/unit test/unit/test.rb].each { |f|
require f }” | unit_diff -u
76111971001011003211511710511610132451011083116971141161011001046107010511010511510410110032105110324846485255565332115101991111101001154610104932116101115116115443249329711511510111411610511111011544324832102971051081171141011154432483210111411411111411510
Strangely I have run my tests individually and they work fine.
I have then tried running autotest in another Rails application and it
works fine.
I have uninstalled and reinstalled all gems related to autotest, and
same problem.
I then deleted my ~/.autotest file so it’s vanilla and that makes no
difference.
Finally, I installed autotest-growl to see what output is coming through
to that, and that works fine and I get the results of my passed / failed
tests, but the console for autotest continues to just pump out a string
of numbers instead of a description of the tests it is running.
I am using ruby 1.8.7
The following gems are installed:
autotest (4.2.9)
autotest-growl (0.2.3)
autotest-rails (4.1.0)
I have tried enabling and disabling redgreen, but to no avail.
Please can someone help me, I am absolutely stumped.
Matt
Hi Matt,
I have the same misbehavior after update the gems,the autotest’s output
is
garbled and if I hit Ctrl-C once (to run the specs again) I got this
error:
usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/formatter/progress_bar_formatter.rb:16:in
write': Broken pipe (Errno::EPIPE) from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/formatter/progress_bar_formatter.rb:16:inprint’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/formatter/progress_bar_formatter.rb:16:in
example_passed' from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/reporter.rb:136:inexample_passed’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/reporter.rb:136:in
each' from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/reporter.rb:136:inexample_passed’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/reporter.rb:31:in
example_finished' from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/example/example_methods.rb:55:inexecute’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/example/example_group_methods.rb:214:in
run_examples' from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/example/example_group_methods.rb:212:ineach’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/example/example_group_methods.rb:212:in
run_examples' from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/example/example_group_methods.rb:103:inrun’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/example_group_runner.rb:23:in
run' from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/example_group_runner.rb:22:ineach’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/example_group_runner.rb:22:in
run' from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/options.rb:152:inrun_examples’
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/command_line.rb:9:in
`run’
from /usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/bin/spec:5
ruby 1.8.6 (2007-09-24 patchlevel 111) [i486-linux]
rspec: 1.3.0
rspec-rails: 1.3.2
ZenTest: 4.3.0
autotest-rails: 4.1.0
FYI - I uninstalled ZenTest-4.3.0 and installed ZenTest-4.2.1 and all is
well:
[sudo] gem uninstall ZenTest
[sudo] gem install ZenTest --version 4.2.1
HTH,
David
On Tue, Mar 30, 2010 at 12:44 PM, Matthew O’riordan
Hi Edgar
I think the error you are saying is a direct result of you hitting Ctl-C
in that you are killing the process and thus the output. Could be
wrong, but I suspect that’s the issue. I get different error messages
every time I hit Ctl-C depending on where in the test execution autotest
is at, so they seem to be transient issues.
I think something to do with the update to the gem has caused the output
to be formatted strangely, but for the life of me I have no idea what
that is.
Matt
More FYI: Ryan released ZenTest 4.3.1 yesterday to address this issue,
so you can upgrade to the latest and greatest.