From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: heads-up: Haskell updates
Date: Fri, 16 Feb 2018 17:14:55 -0500 [thread overview]
Message-ID: <87a7w8lgyo.fsf@netris.org> (raw)
In-Reply-To: <20180216182934.GA21986@jasmine.lan> (Leo Famulari's message of "Fri, 16 Feb 2018 13:29:34 -0500")
Leo Famulari <leo@famulari.name> writes:
> On Fri, Feb 16, 2018 at 07:12:47PM +0100, Marius Bakke wrote:
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>> > Marius Bakke <mbakke@fastmail.com> 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’d prefer building GHC and ghc-resourcet first. We don’t know if this
>> > patch actually fixes our problems. We should merge master into
>> > core-updates again.
>>
>> 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
next prev parent reply other threads:[~2018-02-16 22:15 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:48 heads-up: Haskell updates Ricardo Wurmus
2018-02-14 14:20 ` Ludovic Courtès
2018-02-14 16:46 ` Ricardo Wurmus
2018-02-14 18:46 ` Mark H Weaver
2018-02-14 19:19 ` Ricardo Wurmus
2018-02-14 19:39 ` Ricardo Wurmus
2018-02-14 19:44 ` Ricardo Wurmus
2018-02-14 21:23 ` Mark H Weaver
2018-02-14 21:39 ` Andreas Enge
2018-02-14 22:42 ` Ricardo Wurmus
2018-02-14 22:47 ` Danny Milosavljevic
2018-02-15 8:41 ` Mark H Weaver
2018-02-15 9:17 ` Ricardo Wurmus
2018-02-15 10:38 ` Mark H Weaver
2018-02-15 14:02 ` Timothy Sample
2018-02-15 15:05 ` Ricardo Wurmus
2018-02-17 12:50 ` Ricardo Wurmus
2018-02-17 13:04 ` Ricardo Wurmus
2018-02-17 15:18 ` Andreas Enge
2018-02-17 16:11 ` Ricardo Wurmus
2018-02-17 20:00 ` Mark H Weaver
2018-02-17 20:24 ` core-updates, last call? Leo Famulari
2018-02-17 23:16 ` Ricardo Wurmus
2018-02-18 21:45 ` Pjotr Prins
2018-02-18 22:44 ` Ricardo Wurmus
2018-02-18 20:42 ` heads-up: Haskell updates Chris Marusich
2018-02-15 10:29 ` Mark H Weaver
2018-02-15 11:04 ` Danny Milosavljevic
2018-02-15 11:08 ` Danny Milosavljevic
2018-02-15 11:12 ` Andreas Enge
2018-02-15 15:44 ` Ricardo Wurmus
2018-02-15 17:03 ` Danny Milosavljevic
2018-02-15 17:46 ` Leo Famulari
2018-02-15 18:12 ` Mark H Weaver
2018-02-16 15:26 ` Danny Milosavljevic
2018-02-16 16:31 ` Marius Bakke
2018-02-16 17:43 ` Ricardo Wurmus
2018-02-16 18:12 ` Marius Bakke
2018-02-16 18:29 ` Leo Famulari
2018-02-16 22:14 ` Mark H Weaver [this message]
2018-02-16 18:15 ` Mark H Weaver
2018-02-17 0:33 ` Ricardo Wurmus
2018-02-17 12:11 ` Oleg Pykhalov
2018-02-17 12:18 ` Ricardo Wurmus
2018-02-17 12:55 ` Oleg Pykhalov
2018-02-17 13:00 ` Ricardo Wurmus
2018-02-17 13:38 ` Timothy Sample
2018-02-17 14:42 ` Ricardo Wurmus
2018-02-17 16:04 ` Timothy Sample
2018-02-17 23:22 ` Ricardo Wurmus
2018-02-17 15:51 ` Oleg Pykhalov
2018-02-17 19:48 ` Mark H Weaver
2018-02-17 19:54 ` Mark H Weaver
2018-02-17 21:51 ` Danny Milosavljevic
2018-02-17 22:32 ` Timothy Sample
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7w8lgyo.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).