Version: 2.56.0-2
On Tue, 27 Dec 2016, Simon McVittie wrote:
> On Tue, 27 Dec 2016 at 12:22:03 +0100, Santiago Vila wrote:
> > Cc:ing also Simon McVittie: I have not tested version 2.56.0-2 yet,
> > sorry. Is it likely or possible that the changes in such version make
> > the failing tests I expe
On Tue, 27 Dec 2016 at 12:22:03 +0100, Santiago Vila wrote:
> Cc:ing the submitter, who also happen to be a Release Manager.
> I wish we would not lower our standards to allow packages like
> this one to FTBFS as much as they want as a normal thing.
Speaking as a maintainer of a package whose test
On Tue, 2016-12-27 at 12:22 +0100, Santiago Vila wrote:
> Cc:ing the submitter, who also happen to be a Release Manager.
Slight nitpick, but "only" a Stable Release Manager these days.
Regards,
Adam
On Sat, 1 Jun 2013, Adam D. Barratt wrote:
> Source: libsoup2.4
> Version: 2.42.2-4
> Tags: jessie sid
> Severity: serious
>
> Hi,
>
> libsoup2.4 FTBFS on several architectures with test failures; [...]
Still the case three years later: FTBFS randomly with test failures.
I've built this packag
tags 710696 + patch
thanks
Hi,
I can no longer reproduce the test failures in current sid on
kfreebsd-amd64. (Except, two test failures that I would expect due to
my jail/chroot configuration).
Please consider re-enabling the testsuite on non-Linux platforms, before
closing this bug. Thanks!
severity 710696 important
thanks
Temporarily downgraded the severity as I disabled the test suite on !linux as
this was blocking many packages from migrating to testing. I plan on re-enabling
the test suite again so let's keep this open. Any help on investigating it is
welcome.
On 16/06/13 01:17,
On 15/06/13 23:53, Emilio Pozuelo Monfort wrote:
> On 11/06/13 22:28, Steven Chamberlain wrote:
>> Sometimes it completes the whole testsuite, in which case it (always)
>> returns 2 errors instead:
>>
>>> External helper support
>>
>>> Round 2: NTLM Connection, user=alice
>>> (S:sent) (S:alice) /
Hi,
Thanks for the info!
On 11/06/13 22:28, Steven Chamberlain wrote:
> Hi,
>
> On kfreebsd-* arches it is the lt-ntlm-test that doesn't finish and
> causes the build process to hang.
>
> In the buildd logs its output is not shown, probably being buffered
> somehow, but running it manually it g
Hi,
On kfreebsd-* arches it is the lt-ntlm-test that doesn't finish and
causes the build process to hang.
In the buildd logs its output is not shown, probably being buffered
somehow, but running it manually it gets stuck here:
> External -> fallback support
> Round 1: Non-NTLM Connection, no aut
Emilio Pozuelo Monfort dixit:
>I see timeout-test is failing there as well. That shouldn't be because the arch
>is slow. There's probably a bug somewhere, maybe libsoup, that only manifests
>in
>sparc and m68k. See https://bugzilla.gnome.org/show_bug.cgi?id=660581
Ah okay.
>I just tried today t
On 07/06/13 22:48, Thorsten Glaser wrote:
> Hi,
>
> it also fails the testsuite on m68k, but only with timeouts
> due to the slowness of the architecture I think.
>
> Please have a look at the build logs here too:
> http://buildd.debian-ports.org/status/package.php?p=libsoup2.4
>
> I’d be glad i
Hi,
it also fails the testsuite on m68k, but only with timeouts
due to the slowness of the architecture I think.
Please have a look at the build logs here too:
http://buildd.debian-ports.org/status/package.php?p=libsoup2.4
I’d be glad if you could just disable the two offending
tests on m68k.
T
Source: libsoup2.4
Version: 2.42.2-4
Tags: jessie sid
Severity: serious
Hi,
libsoup2.4 FTBFS on several architectures with test failures; from the
armel build log:
soup_uri_new (NULL)
Got expected warning: soup_uri_new_with_base: assertion `base == NULL
|| SOUP_URI_IS_VALID (base)' failed
Go
13 matches
Mail list logo
