[Debichem-devel] Bug#1049526: gromacs: Fails to build binary packages again after successful build
Lucas Nussbaum
lucas at debian.org
Wed Aug 16 08:42:49 BST 2023
Source: gromacs
Version: 2023.2-2
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian-qa at lists.debian.org
Usertags: qa-doublebuild
Hi,
This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild
Relevant part of the build log:
> 99% tests passed, 1 tests failed out of 87
>
> Label Time Summary:
> GTest = 792.43 sec*proc (83 tests)
> IntegrationTest = 671.70 sec*proc (27 tests)
> MpiTest = 725.49 sec*proc (21 tests)
> QuickGpuTest = 623.87 sec*proc (17 tests)
> SlowGpuTest = 125.13 sec*proc (14 tests)
> SlowTest = 99.18 sec*proc (13 tests)
> UnitTest = 21.55 sec*proc (43 tests)
>
> Total Test time (real) = 792.58 sec
>
> The following tests FAILED:
> 72 - MdrunMultiSimReplexTests (Timeout)
> Errors while running CTest
> make: *** [debian/rules:126: build-mpi] Error 8
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -b' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/16/gromacs_2023.2-2_unstable.log
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
More information about the Debichem-devel
mailing list