Hi Feri,
> > And it succeeded. I can't really draw any conclusion from this. I'll
> > run the tests locally for some more time, maybe eventually it
> > reproduces in my setup as well...
>
> I forgot about this, so the test ran 12659 times successfully before I
> broke the loop.
Oh dear, and I
wf...@niif.hu writes:
> Mattia Rizzolo writes:
>
>> I'm also a bit of a loss as to what might be happening here, so the best
>> I could do right now is to manually schedule another build (for unstable
>> only at this time).
>> Let's see.
>
> And it succeeded. I can't really draw any conclusion f
On Fri, Jul 26, 2019 at 04:58:00PM -0300, Chris Lamb wrote:
> Ah, getcha, so build systems / test were failing to resolve "localhost"
> rather than the underlying 127.0.0.1 loopback device being missing or
> broken, etc.?
Usually, that was it. At least the ones I had a chance to look at.
Indeed,
Mattia Rizzolo wrote:
> After some deliberation between pbuilder maintainers, sbuild
> maintainers, d-policy people, interested 3rd parties, etc, we came to
> the conclusion that is the chroot's manager job to provide a useful
> /etc/hosts, i.e. pbuilder's job in this case.
Ah, getcha, so build s
[ OT: why do you seem to label the mailing list with the name "Apple"? ]
On Fri, Jul 26, 2019 at 03:08:47PM -0300, Chris Lamb wrote:
> > whilst it's true that in the past localhost would not always resolv to
> > 127.0.0.1, I now fixed it in pbuilder itself
>
> Ah, that was it? This resolves (get
Mattia Rizzolo wrote:
> > Not 100% sure but I thnk the second build also has a slightly
> > different networking setup […]
>
> Not afaik, we don't do any kind of changes to the network setup, and
> whilst it's true that in the past localhost would not always resolv to
> 127.0.0.1, I now fixed
On Thu, Jul 25, 2019 at 06:17:23PM -0300, wf...@niif.hu wrote:
> As
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
> shows, the first build succeeds, but the second one hits a failure in
> the build time unit tests. This has been rather consistent for several
>
Mattia Rizzolo writes:
> On Thu, Jul 25, 2019 at 11:10:51PM -0300, Chris Lamb wrote:
>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
>>> shows, the first build succeeds, but the second one hits a failure in
>>> the build time unit tests. This has been rathe
On Thu, Jul 25, 2019 at 11:10:51PM -0300, Chris Lamb wrote:
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
> > shows, the first build succeeds, but the second one hits a failure in
> > the build time unit tests. This has been rather consistent for several
> >
Hi Feri,
> As
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
> shows, the first build succeeds, but the second one hits a failure in
> the build time unit tests. This has been rather consistent for several
> uploads.
Not 100% sure but I thnk the second bu
Hi,
As
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
shows, the first build succeeds, but the second one hits a failure in
the build time unit tests. This has been rather consistent for several
uploads. What are my options for tracking down this problem?
--
T
11 matches
Mail list logo
