Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-08-26 Thread Paul Gevers
Hi all, On Sat, 4 Aug 2018 18:48:44 +0200 Aurelien Jarno wrote: > On 2018-07-23 22:17, Paul Gevers wrote: > > On Sun, 01 Apr 2018 21:56:33 +0200 Florian Weimer > > wrote: > > > > I have no idea. On a fast 4-cores amd64 machine and for the 3 flavours > > > > built on amd64, the glibc takes

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-08-04 Thread Aurelien Jarno
On 2018-07-23 22:17, Paul Gevers wrote: > On Sun, 01 Apr 2018 21:56:33 +0200 Florian Weimer wrote: > > > I have no idea. On a fast 4-cores amd64 machine and for the 3 flavours > > > built on amd64, the glibc takes around 20 minutes to build and the > > > testsuite around 2h to run. > > > > This

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-08-04 Thread Aurelien Jarno
On 2018-07-30 23:14, Florian Weimer wrote: > * Paul Gevers: > > > Hi Florian, > > > > On 29-07-18 13:26, Florian Weimer wrote: > >> I'm not sure why it is necessary to build glibc three times (unless > >> it's impossible to get multi-arch packages into the buildroot). > > > > I am not sure if I

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-07-31 Thread Paul Gevers
Hi Florian, On 30-07-18 23:14, Florian Weimer wrote: > * Paul Gevers: >> On 29-07-18 13:26, Florian Weimer wrote: >>> I'm not sure why it is necessary to build glibc three times (unless >>> it's impossible to get multi-arch packages into the buildroot). >> >> I am not sure if I understand what

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-07-30 Thread Florian Weimer
* Paul Gevers: > Hi Florian, > > On 29-07-18 13:26, Florian Weimer wrote: >> I'm not sure why it is necessary to build glibc three times (unless >> it's impossible to get multi-arch packages into the buildroot). > > I am not sure if I understand what you mean, but currently having > multiple

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-07-29 Thread Paul Gevers
Hi Florian, On 29-07-18 13:26, Florian Weimer wrote: > I'm not sure why it is necessary to build glibc three times (unless > it's impossible to get multi-arch packages into the buildroot). I am not sure if I understand what you mean, but currently having multiple arches available in the

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-07-29 Thread Florian Weimer
* Paul Gevers: > On Sun, 01 Apr 2018 21:56:33 +0200 Florian Weimer wrote: >> > I have no idea. On a fast 4-cores amd64 machine and for the 3 flavours >> > built on amd64, the glibc takes around 20 minutes to build and the >> > testsuite around 2h to run. >> >> This is still rather slow. I see

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-07-23 Thread Paul Gevers
On Sun, 01 Apr 2018 21:56:33 +0200 Florian Weimer wrote: > > I have no idea. On a fast 4-cores amd64 machine and for the 3 flavours > > built on amd64, the glibc takes around 20 minutes to build and the > > testsuite around 2h to run. > > This is still rather slow. I see native builds on

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-04-02 Thread Florian Weimer
* Aurelien Jarno: > I have no idea. On a fast 4-cores amd64 machine and for the 3 flavours > built on amd64, the glibc takes around 20 minutes to build and the > testsuite around 2h to run. This is still rather slow. I see native builds on relatively current hardware taking 2 minutes, plus 12

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-03-14 Thread Aurelien Jarno
On 2018-03-14 07:40, Paul Gevers wrote: > Hi Aurelien, > > On 14-03-18 00:15, Aurelien Jarno wrote: > > On 2018-03-13 21:13, Paul Gevers wrote: > >> On Mon, 18 May 2015 15:47:34 -0300 Antonio Terceiro > >> wrote: > >>> The glibc test runs times out at ci.debian.net after

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-03-14 Thread Paul Gevers
Hi Aurelien, On 14-03-18 00:15, Aurelien Jarno wrote: > On 2018-03-13 21:13, Paul Gevers wrote: >> On Mon, 18 May 2015 15:47:34 -0300 Antonio Terceiro >> wrote: >>> The glibc test runs times out at ci.debian.net after running for ~3h, >>> apparently since they were

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-03-14 Thread Aurelien Jarno
On 2018-03-13 21:13, Paul Gevers wrote: > On Mon, 18 May 2015 15:47:34 -0300 Antonio Terceiro > wrote: > > The glibc test runs times out at ci.debian.net after running for ~3h, > > apparently since they were introduced: > >

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2018-03-13 Thread Paul Gevers
On Mon, 18 May 2015 15:47:34 -0300 Antonio Terceiro wrote: > The glibc test runs times out at ci.debian.net after running for ~3h, > apparently since they were introduced: > https://ci.debian.net/packages/g/glibc/unstable/amd64/ Is there any hope to have this fixed? > I am

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

2015-05-18 Thread Antonio Terceiro
Source: glibc Severity: normal User: autopkgtest-de...@lists.alioth.debian.org Usertags: autopkgtest Hi, The glibc test runs times out at ci.debian.net after running for ~3h, apparently since they were introduced: http://ci.debian.net/packages/g/gutenprint/unstable/amd64/ It seems that it's