I tried giving ruby-minitest in control file. But, then also, none of
the tests were run. This is the output I got
Running tests for ruby2.1 using debian/ruby-tests.rake ...
/usr/lib/ruby/vendor_ruby/minitest/assertions.rb:17: warning:
already initialized constant MiniTest::Assertions::UNDEFINED
/usr/lib/ruby/2.1.0/minitest/unit.rb:80: warning: previous
definition of UNDEFINED was here
Run options: --seed 27658
# Running tests:
Finished tests in 0.004672s, 0.0000 tests/s, 0.0000 assertions/s.
0 tests, 0 assertions, 0 failures, 0 errors, 0 skips
What is the issue with the two warnings?
On വെള്ളി 09 ജനുവരി 2015 03:01 വൈകു, Cédric Boutillier wrote:
> Hi!
>
> On Fri, Jan 09, 2015 at 01:29:33AM +0530, Pirate Praveen wrote:
>> On Friday 21 November 2014 07:01 PM, Balasankar C wrote:
>>> On 2014-11-21 04:13, Cedric Boutillier wrote:
>>>> Hi Balasankar,
>>>> Strange. It would be useful to have the code of the whole package to try
>>>> to reproduce the problem. Can you push it somewhere?
>>> Yes. I've pushed it to
>>> https://gitlab.com/balasankarc/ruby-actionpack-page-caching
>>> Sorry about that underscore, it was a typo.
>>>
>> can anyone try building this package and fixing the issue?
> It seems that the problem is that the wrong testing framework is
> indicated in the Build-Depends field. ruby-test-unit is indicated, but
> the package really uses ruby-minitest.
> Replacing ruby-test-unit by ruby-minitest makes the error disappear.
>
> Balasankar, you probably have ruby-minitest installed on your system,
> and it was used implicitly when you built the package with
> dpkg-buildpackage.
>
> Cheers,
>
> Cédric
>
>
Attachment:
signature.asc
Description: OpenPGP digital signature