Override component to main
libunwind 1.0.1-2ubuntu2 in quantal: universe/libs -> main
libunwind-setjmp0 1.0.1-2ubuntu2 in quantal amd64: universe/libs/optional ->
main
libunwind-setjmp0 1.0.1-2ubuntu2 in quantal armel: universe/libs/optional ->
main
libunwind-setjmp0 1.0.1-2ubuntu2 in quantal arm
Override component to main
google-perftools 2.0-3ubuntu1 in quantal: universe/misc -> main
google-perftools 2.0-3ubuntu1 in quantal amd64: universe/devel/optional -> main
google-perftools 2.0-3ubuntu1 in quantal armel: universe/devel/optional -> main
google-perftools 2.0-3ubuntu1 in quantal armhf:
** Changed in: google-perftools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1017972
Title:
[MIR] google-perftools, libunwind
To ma
** Branch linked: lp:ubuntu/google-perftools
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1017972
Title:
[MIR] google-perftools, libunwind
To manage notifications about this bu
Michael
My last upload enabled test suite execution for amd64 and i386
architectures; powerpc has some test failures which I think are related
to the maturity of support for powerpc in this package upstream (4/44
tests fail). I will report this upstream and file an associated LP bug.
Note that f
This bug was fixed in the package google-perftools - 2.0-3ubuntu1
---
google-perftools (2.0-3ubuntu1) quantal; urgency=low
* Enable test suite execution during package build process (LP: #1017972):
- d/rules: Execute check target after build, restrict test execution to
amd
libunwind is fine with tests enabled. Not all platforms, but upstream
makes it difficult to do so. So we at least enable the one platform we
need it for, and that one platform's tests will have to act as our
canary in a coal mine.
** Changed in: libunwind (Ubuntu)
Status: New => Fix Commi
New version of libunwind uploaded with test suite enabled for amd64
only:
libunwind (1.0.1-2ubuntu2) quantal; urgency=low
* Enable test suite for amd64 architecture:
- d/rules: Execute test suite when building for amd64 only.
- d/patches/20122307_fix_setjmp.patch: Cherry picked fix from
libunwind upstream expects a certain number of know failures for each of
the primary archs it supports.
Some of these are documented in the README provided by upstream
x86_64 has the least test failures; I've been able to either cherry pick
fixes or provider workarounds in most of the tests. Two
** Branch linked: lp:~james-page/ubuntu/quantal/google-perftools/test-
suite-enablement
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1017972
Title:
[MIR] google-perftools, libun
I now have a fully functional test suite for google-perftools; proposed
patches submitted back upstream.
Once the glibc fix has been uploaded I will upload this package with the
test suite enabled.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
** Changed in: libunwind (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Changed in: google-perftools (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to li
Reported glibc bug 1028038
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1017972
Title:
[MIR] google-perftools, libunwind
To manage notifications about this bug go to:
https://b
Now hitting this bug in google-perftools -
http://code.google.com/p/gperftools/issues/detail?id=437
** Bug watch added: code.google.com/p/gperftools/issues #437
http://code.google.com/p/gperftools/issues/detail?id=437
--
You received this bug notification because you are a member of Ubuntu
Se
The patch to eglibc fixes the issues with hanging/deadlocked test - two
of which fail for other reasons.
I'll investigate whether quantal will ship eglibc 2.16 or whether we
need to pickup this patch for 2.15
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
This one line patch for eglibc (included in 2.16) may help with the
google-perftools tests:
http://permalink.gmane.org/gmane.comp.lib.glibc.alpha/17093
Testing now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubuntu
I'm not convinced that the deadlock issue in google-perftools is not
caused by the combination of libunwind/glibc that is present in 12.10.
The INSTALL, bug tracker and ML make reference to this being a pain
point on x86_64 - but I see the same issues on other archs.
--
You received this bug not
I've reported the libunwind test failures upstream; however my current
feel is that it won't be possible to gate all architectures using the
test suite as it stands today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubu
** Attachment added: "libunwind-test-failures.txt"
https://bugs.launchpad.net/ubuntu/+source/google-perftools/+bug/1017972/+attachment/3232742/+files/libunwind-test-failures.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunw
After cherry picking one more patch for ARM this branch:
lp:~james-page/ubuntu/quantal/libunwind/tests
Produces the results in the attached document.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubuntu.
https://bugs.la
Micahel
I spent some time digging into the libunwind test failures; from the
large amount of discussion about failing tests on the mailing list it
appears that there are an expected set of failures which vary depending
on architecture.
On x86_64 (5 failures); I was able to cherry pick two fixes (
And for libunwind, adding "$(MAKE) check" after the "$(MAKE)" call will
enable tests. But they have 6 failures, including some segfaults. That
should be investigated as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind i
Enabling the tests for perftools involves a few things:
1) Add "DEB_MAKE_CHECK_TARGET := check" to debian/rules
2) Backport a patch from upstream that fixes tests on i386:
http://code.google.com/p/gperftools/source/detail?r=150
But even then, you run into a deadlock:
http://code.google.com/p/gpe
I think that is probably historic:
libunwind (0.98.5-4) experimental; urgency=low
* Install the unwind library in the libunwind7 package, not libgcc1.
-- Matthias Klose Tue, 3 May 2005 14:50:20 +
So is probably no longer required - but I would defer to Matthias who
probably understand
I thought I had already commented on this one, but I don't see it.
What is the story with the libunwind-setjmp0's diversions of /usr/lib
/libunwind-setjmp.so.0.0.0 and /usr/lib/libunwind-setjmp.so.0? Do any
other packages provide those files?
** Changed in: libunwind (Ubuntu)
Status: New
25 matches
Mail list logo
