From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Let's fix core-updates! Date: Sat, 10 Feb 2018 12:12:16 +0100 Message-ID: <877erljdyn.fsf@elephly.net> References: <876075pne8.fsf@gmail.com> 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]:44376) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ekT59-00010W-Ur for guix-devel@gnu.org; Sat, 10 Feb 2018 06:12:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ekT56-00057S-JA for guix-devel@gnu.org; Sat, 10 Feb 2018 06:12:35 -0500 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21055) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ekT56-00056X-8U for guix-devel@gnu.org; Sat, 10 Feb 2018 06:12:32 -0500 In-reply-to: <876075pne8.fsf@gmail.com> 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: Chris Marusich Cc: guix-devel@gnu.org Hi Chris, thank you for taking the initiative! > Currently, 13% of builds on core-updates fail: > > https://hydra.gnu.org/jobset/gnu/core-updates This may be a better URL: https://hydra.gnu.org/eval/109908?full=3D1&compare=3Dmaster It is a list of build failures that happen on core-updates but not on master. While the growing list of packages that fail to build is a concern it is tangential to getting core-updates merged. > 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? We usually just declare it done when there are no more =E2=80=9Cbig failure= s=E2=80=9D. Looking at the list of ~500 failures I see that we still have failures that are responsible for a lot of other failures. Take =E2=80=9Csbcl=E2=80=9D for example. It is marked red, which means tha= t it failed not because one of its dependencies failed to build, but because there=E2= =80=99s something wrong with it. Sbcl is needed for all the =E2=80=9Csbcl-*=E2=80= =9D packages, which are also needed for =E2=80=9Cuglify-js=E2=80=9D, which in turn is nee= ded for pretty much all of the failing =E2=80=9Cr-*=E2=80=9D packages and for all o= f the =E2=80=9Cjs-*=E2=80=9D packages. So, fixing the =E2=80=9Csbcl=E2=80=9D package appears to be important. The next thing that stands out to me is the long list of =E2=80=9Cjava-*=E2= =80=9D packages that are marked brown, indicating that a dependency failed to build. Turns out that =E2=80=9Cjava-hamcrest-all=E2=80=9D fails to build. = The build error is =E2=80=A6 strange. But maybe we can ignore the Java stuff if we c= an merge the dedicated Java updates branch right after merging core-updates. > 2) How shall we prioritize and divvy up work for fixing the failures? > I'm guessing people just need to volunteer and start debugging! Only the red packages really need investigation. I=E2=80=99ll take a look at these packages: - augeas - knights - python-ipy - sbcl For sbcl we may just be able to upgrade to the latest version. I=E2=80=99m going to give that a try. > 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. I don=E2=80=99t know of any. We can look at the logs of brown packages to = see if we can detect any common dependency failures (as with sbcl above) and we can look at the output of guix graph. But there=E2=80=99s nothing else = I can think of. > 4) What other bugs/features need to be addressed to un-block release? The next release primarily depends on core-updates. As a bonus we can fix a couple more bugs in the bug tracker. I don=E2=80=99t expect us to cu= t a new release right after the merge of core-updates, but that=E2=80=99s the biggest part of it. > 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. Yes, I=E2=80=99d like to get this branch merged before the new release, bec= ause it=E2=80=99s not far from completion. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net