From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: heads-up: Haskell updates Date: Fri, 16 Feb 2018 17:14:55 -0500 Message-ID: <87a7w8lgyo.fsf@netris.org> References: <87zi4b744f.fsf@elephly.net> <20180214234721.4e9fe198@scratchpost.org> <87a7waodaa.fsf@netris.org> <20180215120404.0a96b628@scratchpost.org> <87fu626yvj.fsf@elephly.net> <20180215180340.52db6ded@scratchpost.org> <20180216162642.106e9c7c@scratchpost.org> <87po54vqug.fsf@fastmail.com> <87y3js6da0.fsf@elephly.net> <87k1vcvm5c.fsf@fastmail.com> <20180216182934.GA21986@jasmine.lan> 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]:44843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1emoI7-0005Sm-UF for guix-devel@gnu.org; Fri, 16 Feb 2018 17:15:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1emoI3-00027k-TV for guix-devel@gnu.org; Fri, 16 Feb 2018 17:15:39 -0500 Received: from world.peace.net ([50.252.239.5]:47832) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1emoI3-00027K-N2 for guix-devel@gnu.org; Fri, 16 Feb 2018 17:15:35 -0500 In-Reply-To: <20180216182934.GA21986@jasmine.lan> (Leo Famulari's message of "Fri, 16 Feb 2018 13:29:34 -0500") 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: Leo Famulari Cc: guix-devel Leo Famulari writes: > On Fri, Feb 16, 2018 at 07:12:47PM +0100, Marius Bakke wrote: >> Ricardo Wurmus writes: >>=20 >> > Marius Bakke writes: >> > >> >> Should we do a new merge to get the GHC patch, or just merge >> >> core-updates and let the problem "fix itself" on 'master'? >> > >> > I=E2=80=99d prefer building GHC and ghc-resourcet first. We don=E2=80= =99t know if this >> > patch actually fixes our problems. We should merge master into >> > core-updates again. >>=20 >> As per the discussion on #guix, lfam cherry-picked the GHC patch and a >> new and hopefully final Hydra evaluation is underway. > > The Hydra web interface doesn't show that the previously pending > evaluation has been cancelled and a new evaluation started. Can we make > sure it's doing the right thing? All I did was to push the merge to core-updates. I was short on time and didn't look at Hydra at all. At present, there is a core-updates evaluation pending, but it's quite late in the process--the Scheme code has already finished running--so I'm reluctant to cancel this one. At this late phase of the process, I don't know how to discover which commit it corresponds to, but we'll find out when it's done. Mark