Open ghost opened 14 years ago
I can confirm this bug. Forcing the entire suit to run by interrupting (^C) does not work either anymore.
The changes shown above fix both problems for me.
Sorry for the long delay in getting back to you. Could you please fork, and make a pull request? That way the changes will be logged with your name (so credit goes where credit is due)
Changes fixed me too.
Did this ever get fixed in master? I'm having what appears to be the same issue and I'm not entirely sure how to apply this fix since the code looks different now.
I did no further work on this and I'm completely out of ruby, rails etc. right now, so I hope, somebody else can pick this thread up.
sorry, I didn't want to close the thread
I encountered a strange bug in autotest-inotify and managed to fix it for me. However, my fix looks a bit dirty and so I'll explain the problem:
When running a test with autotest-inotify, everything works fine, until a test failure or error appears. After fixing the failing test, autotests standard behaviour is to run the test and if it passes, reset and run all tests.
However, with autotest-inotify, the "run all tests" step at the end isn't done. The result is, that @known_files is empty and autotest-inotify doesn't find any further tests to run.
My fix included two changes in find_files_to_test(files=nil):
I inserted the if self.last_mtime.to_i == 0 block to check if a reset happened (which means run all tests) and I added the self.find_order.push(*order.sort) because this is where @known_files gets filled.