valgrind failures on armhf (causing other apps to FTBFS)

Bug #1612429 reported by Mario Limonciello
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
valgrind (Ubuntu)
Fix Released
Critical
Dimitri John Ledkov
Yakkety
Fix Released
Critical
Dimitri John Ledkov

Bug Description

fwupd is FTBFS on armhf due to a test suite failure in valgrind armhf 1:3.12.0~svn20160714-1ubuntu1

https://launchpadlibrarian.net/278461990/buildlog_ubuntu-yakkety-armhf.fwupd_0.7.0-0ubuntu7_BUILDING.txt.gz

make[3]: Entering directory '/«PKGBUILDDIR»/libfwupd'
make[4]: Entering directory '/«PKGBUILDDIR»/libfwupd'

valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC) <= 88' failed.
/bin/bash: line 5: 17104 Segmentation fault (core dumped) libtool --mode=execute valgrind --quiet --leak-check=full --show-possibly-lost=no /bin/bash ../test-driver --test-name "$f" --log-file $b.log --trs-file $b.trs --color-tests "$am__color_tests" --enable-hard-errors "$am__enable_hard_errors" --expect-failure "$am__expect_failure" -- "$tst"
make[4]: *** [fwupd-self-test.log] Error 139
Makefile:1249: recipe for target 'fwupd-self-test.log' failed
make[4]: Leaving directory '/«PKGBUILDDIR»/libfwupd'
make[3]: *** [check-TESTS] Error 2

This error has been fixed upstream already. This is the commit.

https://github.com/liquid-mirror/valgrind/commit/662ee1b2a6c546ce7c5e2affd1c5c5f893a12b90

Changed in valgrind (Ubuntu):
assignee: nobody → Dimitri John Ledkov (xnox)
Changed in valgrind (Ubuntu Yakkety):
importance: Undecided → Critical
summary: - valgrind fails on arm
+ valgrind failures on armhf (causing other apps to FTBFS)
tags: added: block-proposed
Changed in valgrind (Ubuntu Yakkety):
status: New → Fix Committed
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Valgrind's autopkgtest caught this too, but later =) So this would not have made it out of proposed anyway.

Removing block proposed tag.

==1767== Memcheck, a memory error detector
==1767== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1767== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==1767== Command: /bin/true
==1767==

valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC) <= 88' failed.
bash: line 1: 1767 Segmentation fault bash -ec 'valgrind /bin/true' 2> >(tee -a /data/adttmp/autopkgtest-lxc.shared.qdy29ymt/downtmp/command1-stderr >&2) > >(tee -a /data/adttmp/autopkgtest-lxc.shared.qdy29ymt/downtmp/command1-stdout)
autopkgtest [22:20:17]: test command1: -----------------------]
command1 FAIL non-zero exit status 139
autopkgtest [22:20:17]: test command1: - - - - - - - - - - results - - - - - - - - - -
autopkgtest [22:20:17]: @@@@@@@@@@@@@@@@@@@@ summary
command1 FAIL non-zero exit status 139

tags: removed: block-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package valgrind - 1:3.12.0~svn20160714-1ubuntu2

---------------
valgrind (1:3.12.0~svn20160714-1ubuntu2) yakkety; urgency=medium

  * Cherry-pick upstream patch to fix assertions on arm. LP: #1612429

valgrind (1:3.12.0~svn20160714-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian (LP: #1567219) remaining changes:
    - Lower over-inflated valgrind-dbg Recommends to Suggests instead.
    - Don't strip vgpreload* on ARM; this results in unusable stack traces
      without valgrind-dbg.
    - Configure with --enable-only64bit on AArch64.

  * Reintroduce universe/valgrind-mpi package, as archive reorg is done.
  * Drop s390x patches, applied upstream.

valgrind (1:3.12.0~svn20160714-1) unstable; urgency=medium

  * New upstream snapshot release
    - Add support for compressed debuginfo (Closes: #810295)
  * Drop MIPS patches (merged/fixed upstream)
  * Refresh patches
  * Add smoke test for autopkgtest
    Thanks to dann frazier for the patch (Closes: #819813)
  * Update 07_fix-spelling-in-binary.patch
  * Update Standards-Version to 3.9.8 (no changes needed)
  * Update Vcs-* URLs

 -- Dimitri John Ledkov <email address hidden> Thu, 11 Aug 2016 23:18:04 +0100

Changed in valgrind (Ubuntu Yakkety):
status: Fix Committed → 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.