carlosbrando / autotest-notification Goto Github PK

Hello

I am using autotest-notification gem with ruby-1.9.2-rc2 (with RVM) and Rails-3.0,0.rc on Ubuntu, and although autotest is working as expected,

  Finished in 0.32554 seconds
 11 examples, 0 failures
  =======================================

the notification is always this:
:( FAIL: 1 Exception occurred.

Autotest and notifications are working well when I use a custom .autotest file.

Thanks
Juanma

Hi Carlos

in the line 30 of lib/autotest_notification.rb has one erro, you are trying to use a variable named 'autotest' but now the name of variable is only 'at'.

Thank you,
Georgeo

First of all: Thanks, I'm using autotest-notifications for several months now and I don't want to miss it anymore.

One thing bugged me thought: You just consider the last line of the output returned by autotest. But if you had failures in different test suites, autotest will run each suite separately. Your implementation notifies just about the last suite. If other plugins like test_benchmark add more lines at the end of the test results, your notifier will report exceptions.

The fix is easy: Consider all lines of the result. I did it the quick & dirty way (without tests and I dropped rspec support, because I don't use it), so you probably won't use my fix, but it works for me: http://github.com/iGEL/autotest-notification/commit/22e1f59d8f91c3c8367829099de351b0f4ee636a

Would like to see a better solution in the main branch, though.

This affects pretty much all autotest notification gems that use notify-send on Linux. Something seems to have changed in notify-send that causes Ctrl-C to not be trapped by autotest anymore. If you press Ctrl-C at any point BEFORE the first notification is sent (ie, while running the tests), it works. Once a notification has been sent, Ctrl-C will no longer work. If you press Ctrl-C, then do something that makes autotest's thread wake up (like Ctrl-Z to background it and fg to bring it back to the foreground), the previous Ctrl-C will be handled. It seems like it's waiting for some signal from notify-send that's no longer getting sent and sleeping until it's found, ignoring all keypresses in the process.

I would like to make the notifications appear less time in the screen.
Is there a way to set this in a configuration file?
Thanks

With the 2.2.0 version of the gem, you get this error if you already have a .autotest file and try to use an-install:

an-install:89: uninitialized constant FileUtils

There doesn't appear to be a require 'fileutils;, which if manually added eliminates the error message.

Hi,

In GNOME 3, critical messages doesn't expire, so I suggest to change their priority to 1 or less. They also stay in the systray after timeout, so I also suggest to add --hint=int:transient:1 to the notify-send call.

I think that these changes make sense, since tests will be executed pretty often with autotest, so it doesn't make sense to have these messages go away only after a mouse click in it.

Best regards!

The autotest gem is now called 'autotest-standalone' instead of just 'autotest'. Requiring 'autotest-notification' will now cause an older version of the autotest gem to be installed (4.4.6, the last one to be called 'autotest').

When I have a test failure, after I alter the code and turn green the tests are executed twice.

I wanted to try if autotest-notification would work with the pure autotest gem, but even if i do a gem install autotest-notification + gem uninstall ZenTest + gem install autotest, autotest_notification fails with:

>> require 'autotest_notification' 
Gem::LoadError: Could not find RubyGem ZenTest (>= 3.9.2)
from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:827:in `report_activate_error'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:261:in `activate'
...

can you remove this runtime dependency (e.g. switch to a simpler require 'autotest'), so all autotest versions can happily use autotest-notification ?