From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Adding build status to the package list table Date: Sat, 21 Nov 2015 16:59:09 +0100 Message-ID: <87r3jj9wdu.fsf@gnu.org> References: <87poz6jgqi.fsf@gnu.org> <877flchhzg.fsf@gnu.org> <87poz4k4eh.fsf@gnu.org> <87610we16l.fsf@gnu.org> <878u5rjry5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36466) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a0AZH-00061P-HM for guix-devel@gnu.org; Sat, 21 Nov 2015 10:59:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a0AZE-0002rS-AB for guix-devel@gnu.org; Sat, 21 Nov 2015 10:59:15 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57424) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a0AZE-0002rO-7L for guix-devel@gnu.org; Sat, 21 Nov 2015 10:59:12 -0500 In-Reply-To: <878u5rjry5.fsf@gnu.org> (Roel Janssen's message of "Sat, 21 Nov 2015 16:24:50 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Roel Janssen Cc: guix-devel@gnu.org Roel Janssen skribis: > Ludovic Court=C3=A8s writes: > >> Roel Janssen skribis: >> >>> Ludovic Court=C3=A8s writes: >>> >>>> Roel Janssen skribis: >>>> >>>>> The list of packages included in Guix [1] provides links to the build >>>>> status of each package in the details. I would like to provide this >>>>> information in a column after "Package details", either as an icon or= as >>>>> a count (e.g. 3/4 builds succeeded). This provides a nicer overview = for >>>>> the current status of the package. >>>> >>>> That=E2=80=99s appealing. However, it entails NUM-ARCHES =C3=97 NUM-P= ACKAGES HTTP >>>> requests, just when loading the page. That seems unreasonable. >>> >>> Maybe we could instead determine the build status at the time we >>> generate the website's package list? >> >> IMO it wouldn=E2=80=99t be very useful since the list is updated once a = day. > > Ok. If we can instead fetch the status of all packages on all > architectures in one HTTP request (using javascript on the client-side), > would that be acceptable? The size of the build status information > should be about the same size as the list of packages. This would be OK, yes. We just need to make sure Hydra executes said request in a reasonable amount of CPU time. Thanks, Ludo=E2=80=99.