unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: No package from hydra
Date: Fri, 19 Aug 2016 17:23:13 +0200	[thread overview]
Message-ID: <20160819152313.GA1274@thebird.nl> (raw)
In-Reply-To: <20160819121903.GA806@thebird.nl>

This overview from hydra is pretty nice and interesting:

  https://hydra.gnu.org/eval/109086?full=1#tabs-still-fail

I wonder if we can present it in such a way that people take note when
a package (they feel responsible for) fails.

I had no idea ldc is failing - and I do feel responsible for that
package.

Pj.

On Fri, Aug 19, 2016 at 02:19:03PM +0200, Pjotr Prins wrote:
> On Fri, Aug 19, 2016 at 02:15:19PM +0200, Pjotr Prins wrote:
> > ldc is broken since May 2016.
> > 
> > http://hydra.gnu.org/job/gnu/master/ldc-0.16.1.x86_64-linux
> > 
> > hmmm.
> 
> Include file gone missing:
> 
> CMakeFiles/LDCShared.dir/dmd2/root/aav.c.o -c /tmp/guix-build-ldc-0.16.1.drv-0/ldc-0.16.1/dmd2/root/aav.c
> 3248/tmp/guix-build-ldc-0.16.1.drv-0/ldc-0.16.1/dmd2/root/port.c: In static member function ���static int Port::isNan(double)���:
> 3249/tmp/guix-build-ldc-0.16.1.drv-0/ldc-0.16.1/dmd2/root/port.c:813:12: error: ���::isnan��� has not been declared
> 3250 return ::isnan(r);
> 3251 ^
> 3252/tmp/guix-build-ldc-0.16.1.drv-0/ldc-0.16.1/dmd2/root/port.c: In static member function ���static int Port::isNan(longdouble)���:
> 3253/tmp/guix-build-ldc-0.16.1.drv-0/ldc-0.16.1/dmd2/root/port.c:829:12: error: ���::isnan��� has not been declared
> 3254 return ::isnan(r);
> 3255 ^
> 3256/tmp/guix-build-ldc-0.16.1.drv-0/ldc-0.16.1/dmd2/root/port.c: In static member function ���static int Port::isInfinity(double)���:
> 3257/tmp/guix-build-ldc-0.16.1.drv-0/ldc-0.16.1/dmd2/root/port.c:857:12: error: ���::isinf��� has not been declared
> 3258 return ::isinf(r);
> 3259 ^
> 
> I am not so much interested in the error. I am interested how we can keep track
> of these failures and notify relevant people.
> 
> Pj.
> 

-- 

  reply	other threads:[~2016-08-19 15:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 11:02 [PATCH v2] gnu: node: Update to 6.3.1 Jelle Licht
2016-08-07  3:00 ` Leo Famulari
2016-08-07 12:45   ` Jelle Licht
2016-08-08 21:18     ` Leo Famulari
2016-08-09 13:13       ` Jelle Licht
2016-08-09 13:18         ` Thompson, David
2016-08-12 17:25         ` Leo Famulari
2016-08-19 10:40           ` Pjotr Prins
2016-08-19 11:04             ` No package from hydra Pjotr Prins
2016-08-19 12:13               ` Pjotr Prins
2016-08-19 12:15                 ` Pjotr Prins
2016-08-19 12:19                   ` Pjotr Prins
2016-08-19 15:23                     ` Pjotr Prins [this message]
2016-08-19 16:03                       ` David Craven
2016-08-30  6:18                     ` Danny Milosavljevic
2016-08-30  8:29                       ` No package from hydra - a proposal for software discovery Pjotr Prins
     [not found]             ` <CAPsKtfLKa9489C6=F1=328y-iZF+wAXJvkdg_HXkA8wSjteu_Q@mail.gmail.com>
2016-08-19 12:16               ` [PATCH v2] gnu: node: Update to 6.3.1 Jelle Licht
2016-08-19 13:39                 ` Jelle Licht
2016-08-19 19:16                   ` Christopher Allan Webber

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=20160819152313.GA1274@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    /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).