clhep: FTBFS: dh_auto_test: make -j1 check returned exit code 2

Bug #1251844 reported by Andreas Moog
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clhep (Debian)
Fix Released
Unknown
clhep (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Imported from Debian bug http://bugs.debian.org/713377:

Source: clhep
Version: 2.1.3.1-1
Severity: serious
Tags: jessie sid
User: <email address hidden>
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[6]: Entering directory `/«PKGBUILDDIR»/Matrix/test'
> make[6]: Nothing to be done for `testBug7328.log'.
> make[6]: Leaving directory `/«PKGBUILDDIR»/Matrix/test'
> fatal: making test-suite.log: failed to create testBug7328.trs
> fatal: making test-suite.log: failed to create testBug7328.log
> make[5]: *** [test-suite.log] Error 1
> make[5]: Leaving directory `/«PKGBUILDDIR»/Matrix/test'
> make[4]: *** [check-TESTS] Error 2
> make[3]: *** [check-am] Error 2
> make[2]: *** [check-recursive] Error 1
> make[1]: *** [check-recursive] Error 1
> dh_auto_test: make -j1 check returned exit code 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/clhep_2.1.3.1-1_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.

Related branches

Andreas Moog (ampelbein)
tags: added: ftbfs trusty
Changed in clhep (Ubuntu):
importance: Undecided → High
Changed in clhep (Debian):
importance: Undecided → Unknown
Andreas Moog (ampelbein)
Changed in clhep (Ubuntu):
status: New → Fix Committed
Revision history for this message
Andreas Moog (ampelbein) wrote :

Well, that worked well... NOT.

The package I uploaded builds fine in a sbuild chroot, but not on the autobuilders and I can't reproduce the test failures. So either we upload a package with the failing tests disabled - or leave as is and hope for upstream to come up with a solution.

Changed in clhep (Ubuntu):
status: Fix Committed → New
Changed in clhep (Debian):
status: New → Fix Released
Revision history for this message
Ross Gammon (rosco2) wrote :

Version 2.1.4.1-1 was released in Debian claiming to fix this bug. But it looks like there are other build failures now.

Changed in clhep (Ubuntu):
status: New → Confirmed
Changed in clhep (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Sebastian Carneiro (scarneiro) wrote :

Bug #713377 refers to another failing test. Changing to #713301, that refers to this same failing test.

Changed in clhep (Debian):
status: Fix Released → Unknown
Changed in clhep (Debian):
status: Unknown → New
Changed in clhep (Ubuntu):
assignee: nobody → Sebastian Carneiro (scarneiro)
Revision history for this message
Sebastian Carneiro (scarneiro) wrote :

I have found a possible fix to this bug. Discussing it with upstream, and waiting for confirmation before proposing that fix here.

Upstream bug: https://savannah.cern.ch/bugs/index.php?104289

Changed in clhep (Debian):
status: New → Fix Released
Changed in clhep (Ubuntu):
status: Triaged → Confirmed
assignee: Sebastian Carneiro (scarneiro) → nobody
tags: added: patch patch-accepted-debian
Revision history for this message
Dmitry Shachnev (mitya57) wrote :

I think this was fixed in https://launchpad.net/ubuntu/+source/clhep/2.1.4.1-1.1. At least that version built fine in archives.

Changed in clhep (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.