On Sat, Oct 31, 2015 at 04:45:54PM +0100, Christian Hofstaedtler wrote: > During a test build your package FTBFS in a ruby2.2-only > environment, as availble in experimental right now. We'd like to > switch to ruby2.2 really soon now, please see the transition bug > #789077 for details. > > Unfortunately the build output didn't give me a hint on what's going > wrong.
This is because ruby-test-unit (the now standalone package) has completely different behavior than the test/unit.rb that's in ruby2.1. The subversion build runs, essentially, “ruby -I /path/to/include/files /path/to/test/run-test.rb”. With ruby2.2 + ruby-test-unit, this doesn't find any tests to run and silently exits with return code 1, causing the build to fail. If I explicitly add “--collector=dir”, then tests run but various tests fail. With ruby2.1 (and ruby-test-unit not installed separately), tests are discovered automatically and all pass fine. It looks like ruby2.1's test/unit.rb is really just a compatibility wrapper, exposing an old test-unit API but using minitest underneath. I'm not sure how easy it will be to port the test suite to either newer test-unit or minitest. This change in behavior is a bit surprising though, especially the silent failure. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <james...@debian.org>
