From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Hartmut Goebel <h.goebel@crazy-compilers.com>, 25177@debbugs.gnu.org
Subject: bug#25177: Test failures don't cause some Python packages to fail
Date: Tue, 20 Dec 2016 14:30:14 -0500 [thread overview]
Message-ID: <20161220193014.GA5450@jasmine> (raw)
In-Reply-To: <8760mebfl4.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
On Tue, Dec 20, 2016 at 07:49:59PM +0100, Marius Bakke wrote:
> Leo Famulari <leo@famulari.name> writes:
> > Bah, I started a new one.
>
> Did this one get cancelled? Perhaps we should merge this to 'staging'
> and deal with any remaining failures when that is ready to be evaluated.
Yes, it looks like that, although I don't know the exact reason. Hydra
has lots of resource management and stability problems.
I guess the python-tests jobset was canceled to free some resources for
the release-0.12.0 jobset.
I'd like to restart python-tests after 0.12.0 is released.
> I believe the vast majority of python packages are now "fixed".
Thank you!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2016-12-20 19:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161211181237.24485-1-ng0@libertad.pw>
[not found] ` <20161211181237.24485-6-ng0@libertad.pw>
2016-12-11 22:34 ` bug#25177: Test failures don't cause some Python packages to fail [was Re: [PATCH 05/11] gnu: Add python-pygit2.] Leo Famulari
2016-12-11 23:04 ` Marius Bakke
2016-12-11 23:05 ` Marius Bakke
2016-12-11 23:23 ` Leo Famulari
2016-12-11 23:34 ` Marius Bakke
2016-12-12 7:54 ` Marius Bakke
2016-12-12 15:44 ` Leo Famulari
2016-12-12 22:23 ` Hartmut Goebel
2016-12-13 9:34 ` Marius Bakke
2016-12-13 20:21 ` bug#25177: Test failures don't cause some Python packages to fail Marius Bakke
2016-12-13 22:11 ` Leo Famulari
2016-12-14 12:11 ` Marius Bakke
2016-12-15 9:26 ` Marius Bakke
2016-12-15 23:55 ` Leo Famulari
2016-12-16 14:02 ` Marius Bakke
2016-12-17 17:14 ` Leo Famulari
2016-12-17 17:38 ` Marius Bakke
2016-12-17 17:56 ` Leo Famulari
2016-12-17 20:15 ` Leo Famulari
2016-12-17 23:47 ` Marius Bakke
2016-12-18 1:28 ` Leo Famulari
2016-12-18 18:55 ` Marius Bakke
2016-12-18 19:04 ` Leo Famulari
2016-12-20 18:49 ` Marius Bakke
2016-12-20 19:30 ` Leo Famulari [this message]
2016-12-24 13:43 ` Marius Bakke
2016-12-24 16:26 ` Leo Famulari
2016-12-26 18:33 ` Leo Famulari
2016-12-16 9:23 ` Hartmut Goebel
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=20161220193014.GA5450@jasmine \
--to=leo@famulari.name \
--cc=25177@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=mbakke@fastmail.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).