On Mon, 18 Dec 2017 at 23:41:50 +, Simon McVittie wrote:
> In 2.54.2-3 I've cut that test down to 1% of the usual repetitions on
> arm64, which seems like enough to prove that this functionality does
> basically work. The fact that it's far slower than on other CPUs is
> still a bug, but
Control: severity 880883 important
On Mon, 18 Dec 2017 at 23:41:50 +, Simon McVittie wrote:
> On Fri, 17 Nov 2017 at 18:37:42 +0100, Emilio Pozuelo Monfort wrote:
> > I gave it back again, and it again got picked by arm-arm-04. With the help
> > from
> > jcristau (as I don't have access to
On Fri, 17 Nov 2017 at 18:37:42 +0100, Emilio Pozuelo Monfort wrote:
> I gave it back again, and it again got picked by arm-arm-04. With the help
> from
> jcristau (as I don't have access to that machine) I determined that the build
> gets killed while running the closures test, which gets
Hi,
On Fri, 17 Nov 2017 18:37:42 +0100 Emilio Pozuelo Monfort
wrote:
> On 12/11/17 15:02, Michael Biebl wrote:
> > Am 05.11.2017 um 13:14 schrieb Michael Biebl:
[...]
> I gave it back again, and it again got picked by arm-arm-04. With the help
> from
> jcristau (as I don't
On 12/11/17 15:02, Michael Biebl wrote:
> Am 05.11.2017 um 13:14 schrieb Michael Biebl:
>> Looking through past build logs, it consistently seems to fail at this
>> point:
>>
>> make[7]: Entering directory
>> '/<>/debian/build/deb/tests/refcount'
>> make closures objects objects2 properties
Am 05.11.2017 um 13:14 schrieb Michael Biebl:
> Looking through past build logs, it consistently seems to fail at this
> point:
>
> make[7]: Entering directory
> '/<>/debian/build/deb/tests/refcount'
> make closures objects objects2 properties properties2 properties3
> properties4 signal1
Looking through past build logs, it consistently seems to fail at this
point:
make[7]: Entering directory
'/<>/debian/build/deb/tests/refcount'
make closures objects objects2 properties properties2 properties3
properties4 signal1 signal2 signal3 signal4 \
make[8]: Entering directory
Source: glib2.0
Version: 2.54.2-1
Severity: serious
As can be seen at
https://buildd.debian.org/status/logs.php?pkg=glib2.0=arm64
glib2.0 FTBFS on arm64 quite often.
Looking through the build history, arm-arm-04 (and to a lesser extent
arm-arm-01) seems to be much more susceptible to build
8 matches
Mail list logo