On Wed, 04 Jan 2017 13:58:38 +0100
Pavel Raiskup <praiskup(a)redhat.com> wrote:
On Wednesday, January 4, 2017 12:06:40 PM CET Pavel Raiskup wrote:
> On Monday, January 2, 2017 3:47:52 PM CET Pavel Raiskup wrote:
> > On Monday, January 2, 2017 2:40:34 PM CET Pavel Raiskup wrote:
> > > Also, the question is whether it isn't really glibc bug, because
> > > schedulers non-ppc64le architectures look to be more "fair"
> > > regardless the default.
> >
> > Sorry, not really -- at least i686 (build cross-compiled from
> > x86_64 probably) is also affected:
> >
https://koji.fedoraproject.org/koji/taskinfo?taskID=17147577
It is nice to see that the build finished in the end (even though it
took ~2 days). So not really infinite ...
... but what worries me is that both builds, even this one,
https://koji.fedoraproject.org/koji/taskinfo?taskID=17147897
finished almost at the same time; both tests took about 48 hours?
Is there some timeout, signal, or scheduler attempt to change
something after 48 hours? :)
there is a timeout set in koji builder config that tells mock to kill
builds after 48 after hours
Dan
> Pavel
>
> > FTR, I just filed:
> >
https://bugzilla.redhat.com/show_bug.cgi?id=1410052
> > Who knows, maybe that could move this forward.
> >
> > That's a result of gnulib discussion:
> >
https://lists.gnu.org/archive/html/bug-gnulib/2017-01/msg00009.html
> >
> > Pavel
> > _______________________________________________
> > devel mailing list -- devel(a)lists.fedoraproject.org
> > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> >
>
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org