From mboxrd@z Thu Jan 1 00:00:00 1970 From: julien lepiller Subject: =?UTF-8?Q?Re=3A_Let=E2=80=99s_freeze_and_build_=E2=80=98core-upd?= =?UTF-8?Q?ates=E2=80=99!?= Date: Tue, 21 Mar 2017 12:16:20 +0100 Message-ID: <40c0a4a513fba9735aa0e4924e238d7b@lepiller.eu> References: <87mvdpw3b3.fsf@gnu.org> <20170320184145.GA5087@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58585) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cqHmC-0002Wj-PM for guix-devel@gnu.org; Tue, 21 Mar 2017 07:16:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cqHmA-0004b3-5q for guix-devel@gnu.org; Tue, 21 Mar 2017 07:16:32 -0400 Received: from dau94-h03-89-91-205-84.dsl.sta.abo.bbox.fr ([89.91.205.84]:59363 helo=skaro.lepiller.eu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cqHm9-0004aE-Oi for guix-devel@gnu.org; Tue, 21 Mar 2017 07:16:30 -0400 Received: from localhost (localhost [127.0.0.1]) by skaro.lepiller.eu (Postfix) with ESMTP id CECBD7FCDD for ; Tue, 21 Mar 2017 12:16:25 +0100 (CET) Received: from skaro.lepiller.eu ([127.0.0.1]) by localhost (lepiller.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cgJlI8fYKBSY for ; Tue, 21 Mar 2017 12:16:21 +0100 (CET) Received: from webmail.lepiller.eu (localhost [127.0.0.1]) by skaro.lepiller.eu (Postfix) with ESMTPA id 87EB17F835 for ; Tue, 21 Mar 2017 12:16:20 +0100 (CET) In-Reply-To: <20170320184145.GA5087@jasmine> 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" To: guix-devel@gnu.org Le 2017-03-20 19:41, Leo Famulari a =C3=A9crit=C2=A0: > On Tue, Feb 14, 2017 at 10:05:04AM +0100, Ludovic Court=C3=A8s wrote: >> So, here=E2=80=99s a plan: >>=20 >> =E2=80=A2 Once Efraim has pushed some of the aarch64 patches, do ano= ther >> evaluation of the =E2=80=9Ccore=E2=80=9D package set for that bran= ch, and check=20 >> for >> anything wrong. From there on, forbid full-rebuild changes. >>=20 >> =E2=80=A2 Once the =E2=80=9Ccore=E2=80=9D subset builds correctly on= all the supported >> platforms (those that Hydra supports), merge =E2=80=98master=E2=80= =99. Maybe=20 >> update >> a couple of things like GnuTLS while we=E2=80=99re at it. From th= ere on >> forbid non-trivial changes. >>=20 >> =E2=80=A2 Build all the packages. (To do that, someone with access = to Hydra >> must change the =E2=80=9Csubset=E2=80=9D argument to =E2=80=9Call=E2= =80=9D in the config of the >> =E2=80=98core-updates=E2=80=99 jobset.) >>=20 >> =E2=80=A2 Fix things. >=20 > We are at this stage... please help :) >=20 > Here is a list of packages that are failing on core-updates but not on > the master branch: >=20 > https://hydra.gnu.org/eval/109549?compare=3Dmaster&full=3D1#tabs-now-fa= il >=20 > It might take a while to load the web page; please have patience :) >=20 > Once you load it, take note of the brown and red icons. >=20 > The brown icon means, "we did not try to build this yet, because one of > the dependencies failed to build". >=20 > The red icon means, "we tried to build this and it failed." You should > probably focus on these failed builds. >=20 > I'm sorry if the color-coding is not sufficient for you; we know it's > not a good system for people who have impaired vision. My vision is > pretty good and I find it hard to pick out the red icons. >=20 > Once you have found an interesting build failure, read its log (the > "raw" log is most useful, in my opinion) and try to reproduce and fix=20 > it > on your machine. Then send a patch! >=20 > Sometimes there is a spurious build failure: The SSH connection used=20 > for > offloading fails, or the build machine is out of memory. Reply to this > thread with a link to the failing build and we will restart it. >=20 > Thanks in advance :) Hi, c-reduce seems to have failed because of a crash in g++. Maybe the=20 server lacked memory? It builds fine here.