Your message dated Mon, 28 Nov 2016 20:58:40 +0100
with message-id
<cakjshr0-amivr27bty9e75zpxywsmndupuxq8h3-j_dsqks...@mail.gmail.com>
and subject line Re: [Pkg-protobuf-devel] Bug#845687: Bug#845687: protobuf:
FTBFS on ppc64el: testMergeFrom segmentation fault
has caused the Debian Bug report #845687,
regarding protobuf: FTBFS on ppc64el: testMergeFrom segmentation fault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
845687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: protobuf
Version: 3.0.0-8
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The latest ppc64el build of protobuf failed:
testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ...
Segmentation fault
debian/rules:42: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 139
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:5: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
Could you please take a look?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Version: 3.0.0-9
On Mon, Nov 28, 2016 at 8:29 PM, Gianfranco Costamagna
<locutusofb...@debian.org> wrote:
>> May you have a local ppc64el machine? What happens if you try the
>> build say three - four times?
>
> now the package is built...
> lets close this bug?
While ppc64el was OK for the first time now, s390x just finished the
building for the second time. The first one was the same issue that
happened on ppc64el. It may be a race in the tests or something
else.as the buildd was different this time.
Anyway, closing.
Laszlo/GCS
--- End Message ---
