From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Please set up hdyra-job for python-branch
Date: Mon, 28 Nov 2016 14:40:03 +0100 [thread overview]
Message-ID: <87d1hfd8p8.fsf@gnu.org> (raw)
In-Reply-To: <583BF716.2060009@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 28 Nov 2016 10:21:26 +0100")
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 26.11.2016 um 05:48 schrieb Leo Famulari:
>> I started the initial evaluation earlier today:
>>
>> https://hydra.gnu.org/jobset/gnu/python-build-system
>
> Thanks. How can I interpret the results? Anything I can or should do?
Of course! :-)
What you can do is compare the failures to current ‘master’ to identify
new problems:
https://hydra.gnu.org/eval/109379?compare=master#tabs-now-fail
As you note, some failures are unrelated transient issues (we’ll restart
those builds), but others may be real.
HTH!
Ludo’.
next prev parent reply other threads:[~2016-11-28 13:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 12:49 Please set up hdyra-job for python-branch Hartmut Goebel
2016-11-26 4:48 ` Leo Famulari
2016-11-28 9:21 ` Hartmut Goebel
2016-11-28 13:40 ` Ludovic Courtès [this message]
2016-11-29 9:54 ` Hartmut Goebel
2016-11-29 14:27 ` Ludovic Courtès
2016-11-29 18:09 ` New python build system merged Hartmut Goebel
2016-11-29 21:12 ` Leo Famulari
2016-11-30 8:20 ` Danny Milosavljevic
2016-11-30 15:02 ` Hartmut Goebel
2016-11-30 16:59 ` Leo Famulari
2016-11-30 17:26 ` Leo Famulari
2016-11-30 17:30 ` Leo Famulari
2016-12-01 14:10 ` Ludovic Courtès
2016-11-30 17:30 ` Hartmut Goebel
2016-11-30 20:41 ` Leo Famulari
2016-12-01 14:13 ` Hydra replacement and all that Ludovic Courtès
2016-11-30 10:41 ` New python build system merged Leo Famulari
2016-11-29 23:46 ` ng0
2016-11-30 12:47 ` Ludovic Courtès
2016-11-30 13:58 ` ng0
2016-11-30 12:40 ` Ludovic Courtès
2016-12-05 19:30 ` Leo Famulari
2016-12-06 9:22 ` Ludovic Courtès
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=87d1hfd8p8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).