[Debian-ha-maintainers] Bug#897508: gfs2-utils: FTBFS: dh_auto_test: make -j8 -Oline check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: gfs2-utils
Version: 3.1.10-2
Severity: serious
Tags: buster sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>/tests'
> /bin/bash 'testsuite' ENABLE_UNIT_TESTS=yes 
> ## ----------------------------- ##
> ## gfs2-utils master test suite. ##
> ## ----------------------------- ##
> 
> mkfs.gfs2 tests
> 
>   1: Locking protocol validation                     ok
>   2: Resource group size validation                  ok
>   3: Journal size validation                         ok
>   4: Block count validation                          ok
>   5: Quota change file size validation               ok
>   6: Locking protocols                               FAILED (mkfs.at:36)
>   7: Valid block sizes 512-4096                      FAILED (mkfs.at:42)
>   8: Max. blocks, min. block size                    FAILED (mkfs.at:50)
>   9: Max. blocks, max. block size                    FAILED (mkfs.at:55)
>  10: Max. resource group size                        FAILED (mkfs.at:60)
>  11: Min. resource group size                        FAILED (mkfs.at:65)
>  12: Max. resource group size, min. block size       FAILED (mkfs.at:70)
>  13: Max. journal size                               FAILED (mkfs.at:75)
>  14: Min. journal size                               FAILED (mkfs.at:80)
>  15: Max. quota change file size                     FAILED (mkfs.at:85)
>  16: Min. quota change file size                     FAILED (mkfs.at:90)
>  17: Lock table validation                           FAILED (mkfs.at:98)
>  18: Device i/o limits handling                      FAILED (mkfs.at:107)
> 
> fsck.gfs2 tests
> 
>  19: Fix invalid block sizes                         FAILED (fsck.at:6)
>  20: Fix invalid goal blocks                         FAILED (fsck.at:15)
>  21: Fix bad resource group #0                       FAILED (fsck.at:20)
>  22: Fix bad resource group #1                       FAILED (fsck.at:25)
>  23: Fix bad rindex entry #1                         FAILED (fsck.at:35)
> 
> gfs2_edit tests
> 
>  24: Save/restoremeta, defaults                      FAILED (edit.at:7)
>  25: Save/restoremeta, no compression                FAILED (edit.at:20)
>  26: Save/restoremeta, min. block size               FAILED (edit.at:30)
>  27: Save/restoremeta, 4 journals                    FAILED (edit.at:40)
>  28: Save/restoremeta, min. block size, 4 journals   FAILED (edit.at:50)
> 
> libgfs2 unit tests
> 
>  29: meta.c                                          FAILED (libgfs2.at:4)
>  30: rgrp.c                                          ok
> 
> ## ------------- ##
> ## Test results. ##
> ## ------------- ##
> 
> ERROR: All 30 tests were run,
> 24 failed unexpectedly.
> ## -------------------------- ##
> ## testsuite.log was created. ##
> ## -------------------------- ##
> 
> Please send `tests/testsuite.log' and all information you think might help:
> 
>    To: <linux-cluster at redhat.com>
>    Subject: [gfs2-utils master] testsuite: 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 failed
> 
> You may investigate any problem if you feel able to do so, in which
> case the test suite provides a good starting point.  Its output may
> be found below `tests/testsuite.dir'.
> 
> make[3]: *** [Makefile:811: check-local] Error 1
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/tests'
> make[2]: *** [Makefile:665: check-am] Error 2
> make[1]: *** [Makefile:462: check-recursive] Error 1
> dh_auto_test: make -j8 -Oline check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/gfs2-utils_3.1.10-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.