From: Robert Vollmert <rob@vllmrt.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: ci for wip-haskell-updates
Date: Mon, 22 Jul 2019 21:50:49 +0200 [thread overview]
Message-ID: <99509849-CFA2-4729-8FDC-D1A7798C73ED@vllmrt.net> (raw)
In-Reply-To: <87muh5dhax.fsf@elephly.net>
Hi Ricardo,
> On 22. Jul 2019, at 21:01, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> Now I was wondering how to get CI to test that.
>
> Adding branches is currently done manually. I’ll just update the
> table of branches to build on ci.guix.gnu.org in a few minutes.
nice, thanks!
The current status of the evaluation of wip-haskell-updates is quite
confusing. There are a number of jobs listed as “Scheduled” with a red
X mark at the front. Is this a bug?
>> (By the way there’s a branch wip-haskell that hasn’t been touched
>> in a while, should we delete it?)
>
> Looks like I last touched it. It should probably be deleted.
I tried:
$ git push guix :wip-haskell
remote: fatal: bad object 0000000000000000000000000000000000000000
remote: Sending notification emails to: guix-commits@gnu.org
^C
I have a bad feeling about the fact that it hung sending notification
emails though — hope this didn’t spam guix-commits…
Robert
next prev parent reply other threads:[~2019-07-22 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 17:39 ci for wip-haskell-updates Robert Vollmert
2019-07-22 19:01 ` Ricardo Wurmus
2019-07-22 19:50 ` Robert Vollmert [this message]
2019-07-22 20:44 ` Robert Vollmert
2019-07-22 20:57 ` Robert Vollmert
2019-07-25 17:38 ` Ludovic Courtès
2019-07-31 14:52 ` Robert Vollmert
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=99509849-CFA2-4729-8FDC-D1A7798C73ED@vllmrt.net \
--to=rob@vllmrt.net \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).