Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libhostfile-manager-perl: FTBFS: You planned 65 tests but ran 64. #8

Open
gregoa opened this issue Aug 31, 2021 · 0 comments
Open

libhostfile-manager-perl: FTBFS: You planned 65 tests but ran 64. #8

gregoa opened this issue Aug 31, 2021 · 0 comments

Comments

@gregoa
Copy link

gregoa commented Aug 31, 2021

We have the following bug reported to the Debian package of
Hostfile-Manager, c.f. https://bugs.debian.org/993397

It doesn't seem to be a bug in the packaging, so you may want to take
a look. Thanks!

------8<-----------8<-----------8<-----------8<-----------8<-----

Source: libhostfile-manager-perl
Version: 0.09-1.1
Severity: serious
Tags: ftbfs sid bookworm

This package fails its test suite on current sid.

It probably broke with libtest-nowarnings-perl_1.06-1 which is already
in testing (not sure why autopkgtest regression checks didn't catch this.)
From the Test-NoWarnings changelog:

  Made had_no_warnings turn off the checking at END time for use with
  done_testing based tests with no test count. Also added docs.

From https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libhostfile-manager-perl.html

   # Looks like you planned 65 tests but ran 64.
   t/run.t .. 
   1..65
   ok 1 - use Hostfile::Manager;
   ok 2 - Hostfile::Manager->can('block')
   ok 3 - block
   ok 4 - Hostfile::Manager->can('new')
   ok 5 - ... and the constructor should succeed
   ok 6 - '... and the object it returns' isa 'Hostfile::Manager'
   ok 7 - Hostfile::Manager->can('disable_fragment')
   ok 8 - ... and fragment_enabled returns ok when fragment is indeed enabled
   ok 9 - ... and disable_fragment returns ok when fragment is newly disabled
   ok 10 - ... and fragment is indeed disabled
   ok 11 - Hostfile::Manager->can('enable_fragment')
   ok 12 - ... and enable_fragment returns ok when fragment is newly enabled
   ok 13 - ... and fragment is indeed enabled
   ok 14 - Hostfile::Manager->can('enable_fragment')
   ok 15 - ... and enable_fragment returns ok when fragment is newly enabled
   ok 16 - ... and fragment is indeed enabled
   ok 17 - ... and fragment only appears once
   ok 18 - ... and enable_fragment does not complain excessively when enabling missing fragment
   ok 19 - Hostfile::Manager->can('fragment_enabled')
   ok 20 - ... and fragment_enabled returns ok when fragment is indeed enabled
   ok 21 - ... and fragment_enabled returns not_ok when fragment is not enabled
   ok 22 - Hostfile::Manager->can('fragment_list')
   ok 23 - ... and fragment list matches expectation
   ok 24 - Hostfile::Manager->can('fragment_status_flag')
   ok 25 - ... and fragment_status_flag returns '+' when fragment is enabled and unmodified
   ok 26 - ... and fragment_status_flag returns '*' when fragment is enabled and modified
   ok 27 - ... and fragment_status_flag returns ' ' when fragment is disabled
   ok 28 - Hostfile::Manager->can('get_fragment')
   ok 29 - ... and get_fragment returns fragment content
   ok 30 - Hostfile::Manager->can('get_fragment')
   ok 31 - ... and get_fragment undef when fragment file missing
   ok 32 - Hostfile::Manager->can('hostfile')
   ok 33 - ... and hostfile should start out with content of file at hostfile_path
   ok 34 - ... and settings its value should NOT succeed
   ok 35 - ... and settings its value did not succeed
   ok 36 - hostfile should start out with content of file at hostfile_path
   ok 37 - Hostfile::Manager->can('hostfile')
   ok 38 - ... and hostfile should start out with content of file at hostfile_path, even when constructed with a different hostfile_path
   ok 39 - Hostfile::Manager->can('hostfile_path')
   ok 40 - ... and hostfile_path should start out with default value
   ok 41 - ... and setting its value should succeed
   ok 42 - Hostfile::Manager->can('load_hostfile')
   ok 43 - ... and load_hostfile indicates success
   ok 44 - ... and load_hostfile actually loaded the file
   ok 45 - Hostfile::Manager->can('load_hostfile')
   ok 46 - ... and load_hostfile chokes when hostfile missing
   ok 47 - Hostfile::Manager->can('load_hostfile')
   ok 48 - ... and load_hostfile indicates success
   ok 49 - ... and load_hostfile actually loaded the file
   ok 50 - Hostfile::Manager->can('path_prefix')
   ok 51 - ... and path_prefix should start out with default value
   ok 52 - ... and setting its value should succeed
   ok 53 - Hostfile::Manager->can('toggle_fragment')
   ok 54 - ... and fragment_enabled returns ok when fragment is enabled
   ok 55 - ... and toggle_fragment returns ok when fragment is newly toggled
   ok 56 - ... and fragment is disabled
   ok 57 - ... and toggle_fragment returns ok when fragment is newly toggled
   ok 58 - ... and fragment is enabled
   ok 59 - Hostfile::Manager->can('write_hostfile')
   ok 60 - ... and write_hostfile returns ok
   ok 61 - ... and hostfile written to t/fixtures/hosts/write_test
   ok 62 - Hostfile::Manager->can('write_hostfile')
   ok 63 - ... and write_hostfile chokes when trying to write to file without permissions
   ok 64 - ... and hostfile NOT written to t/fixtures/hosts/write_test
   Dubious, test returned 255 (wstat 65280, 0xff00)
   Failed 1/65 subtests 
   
   Test Summary Report
   -------------------
   t/run.t (Wstat: 65280 Tests: 64 Failed: 0)
     Non-zero exit status: 255
     Parse errors: Bad plan.  You planned 65 tests but ran 64.

-- 
Niko Tyni   ntyni@debian.org


------8<-----------8<-----------8<-----------8<-----------8<-----

Thanks for considering,
gregor herrmann,
Debian Perl Group

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant