https://bugzilla.redhat.com/show_bug.cgi?id=786636 --- Comment #13 from Guillermo Gómez <guillermo.gomez@xxxxxxxxx> --- (In reply to Vít Ondruch from comment #5) > (In reply to comment #4) > Not sure what is the issue with the test suite, but if you run the tests > independently, there is no point to execute them using testrb. You should be > able to run them by ruby itself. > > Also, you can always omit testrb by using something like: > > $ ruby -e "Dir.glob('./test/**/*_test.rb').each {|t| require t}" > > to execute the whole test suite at once. Well yes, that's ideal, but the point of running them independently is to be able to avoid a particular test and make the packaging succeed, no need sometimes to force every single test to pass for packaging needs, perhaps there are non sense test for our environments. This is also a result instead of failing tests previously, so also worked for me to isolate things. BTW thanks for the great tips :) I keep using testrb just as a good practice and consistency and readability, hope this is not a blocker. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review