On 2018-06-28 23:04:59, Chris Lamb wrote:
> Hey Antoine,
>
>> I am not sure why the test suite fails nor why the output varies from
>> one build to the next. Once a package is built, however, it passes the
>> test suite reliably.
>
> That may be, but as we only (*) really care about the package bui
Hey Antoine,
> I am not sure why the test suite fails nor why the output varies from
> one build to the next. Once a package is built, however, it passes the
> test suite reliably.
That may be, but as we only (*) really care about the package building
reliably, *subsequent* runs of the testsuite
On 2018-06-28 21:56:07, Chris Lamb wrote:
> Hey Antoine, :)
>
>> The package I managed to build obviously passes that test suite, and
>> *reliably* [but] it might FTBFS on the buildds
>
> Thanks for working on this. :)
>
> I'm a bit lost by your wording; it "might" FTBFS on the buildds, it
> does n
Hey Antoine, :)
> The package I managed to build obviously passes that test suite, and
> *reliably* [but] it might FTBFS on the buildds
Thanks for working on this. :)
I'm a bit lost by your wording; it "might" FTBFS on the buildds, it
does not sound particularly reliable to me… and thus doesn't
Hi,
I have worked on porting the security issues fixed in wheezy into jessie
for the Mercurial package, as I previously mentioned here.
I was not able to make the package build reproducibly. The test suite
fails during the build because of an ordering issue in the `hg serve`
output and I cannot f
