From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Let's fix core-updates! Date: Sat, 10 Feb 2018 03:51:59 +0100 Message-ID: <876075pne8.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36858) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ekLGu-0001Ml-Tm for guix-devel@gnu.org; Fri, 09 Feb 2018 21:52:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ekLGu-0006xI-3i for guix-devel@gnu.org; Fri, 09 Feb 2018 21:52:12 -0500 Received: from mail-it0-x22a.google.com ([2607:f8b0:4001:c0b::22a]:34710) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ekLGt-0006x2-UV for guix-devel@gnu.org; Fri, 09 Feb 2018 21:52:12 -0500 Received: by mail-it0-x22a.google.com with SMTP id j21so867215ita.1 for ; Fri, 09 Feb 2018 18:52:11 -0800 (PST) Received: from garuda.local ([2601:602:9d02:4725:6495:ba21:1ebe:620a]) by smtp.gmail.com with ESMTPSA id e132sm418989itb.30.2018.02.09.18.52.08 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 09 Feb 2018 18:52:09 -0800 (PST) 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 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi everyone! Currently, 13% of builds on core-updates fail: https://hydra.gnu.org/jobset/gnu/core-updates We need to fix this to help Ricardo prepare for the next release. Questions: 1) When is core-updates "done"? Do we merge once we're below a specific failure rate, once specific bugs have been fixed, or a combination of the two? 2) How shall we prioritize and divvy up work for fixing the failures? I'm guessing people just need to volunteer and start debugging! 3) Are there any tools to help us understand what the failures might have in common? E.g., if half the failures occur because a package deep in the dependency graph fails to build, clearly that package should be prioritized for fixing. I suppose we'll learn about commonalities as we go, but it'd be nice if there were a tool that might help us understand what to focus on first. 4) What other bugs/features need to be addressed to un-block release? I know that we want to update the default JDK used by Java packages from 7 to 8, but there are probably more important tasks to finish up, also. Let's get started! =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlp+Xk8ACgkQ3UCaFdgi Rp1jMQ/9EnOCaB84iUjx96X40v6jxrmqcv3Etkssa259pStVchYlBfPkGo5y32tJ ext2j2jSzU/o9Jc2bD/Nz2QxDc8KxuvEQbhHgaTQ7w2Xl26ylRfczC9Qg/Nq6iJY lNwhRQeRuuH0Vda9KwJOl1HtwOW/QHy2I7S4Ss5RmPPpbQKupJ1kcpNT3lNNl4U/ v73YcI25tCZ+a+nZS6tMURX78k4+b+/kJD3qoravStDw89JY8yg7CisdMa/0i5CD BQ8sdm6tJswoAxJ4aR2g8ovIlFZFBaEHxVw2jQc6BL5xMZ1wghJzE2qgUfH4JHpd FNMb5ZCMYUPDEmU3GCFbgF1P98g2YZx4Dzo3yJIe0d/WI39eyecsr7/M6yYjc3B/ /Hj0ASbVdYWalMBl5mdKMH0V8bT8MNt12XsNz6YTUA91pHii5febq9FDogf/kdOv HXphB0Ir3DoxtnNw5fMkf0yLqMilwYu9dr1VNpULj4x+O0D+T9xLUDTcS/tkU3QB oD3meKFAV/ERbZNNdoeAVA3Lp+V1QuLHhQX3rp+zvhKxkKpz/xnFwPRGuVn/mkJo fFEEjsBXQAyML/aDe1IMiFsAx4eha/cNVmVJlaXerHmoidQFu8QLT4FpM0Nffn9o V6X0bQbnt372x8cK53EavwnQsjXOnEz9N54XprKMBnovSC7okJs= =PpZX -----END PGP SIGNATURE----- --=-=-=--