all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Release 1.2.1: python2-pylibmc and libmemcached
Date: Tue, 16 Mar 2021 07:48:07 -0400	[thread overview]
Message-ID: <87r1kfqpzc.fsf@gmail.com> (raw)
In-Reply-To: <86o8fkdcil.fsf@gmail.com> (zimoun's message of "Mon, 15 Mar 2021 09:52:50 +0100")

Hi Simon,

zimoun <zimon.toutoune@gmail.com> writes:

> Hi,
>
> On Sat, 13 Mar 2021 at 20:58, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> zimoun <zimon.toutoune@gmail.com> writes:
>
>>> takes ages.  Does it make sense to add something like:
>>>
>>>       (properties
>>>        `((max-silent-time . 14400))) ; 4 hours, expected even on x86_64
>
>> libmemcached still seems like a fine package to have in Guix.  I say, if
>> the above change is enough to have it built by the CI, I think it's what
>> we should do :-).
>
> On my machine, the build of libmemcached takes ~5min without the tests.
> And with the test suite, it takes ~570min.  Well, I have been too lazy
> to remove the offending test which takes ages, and compare.  I do not
> know if Cuirass fails to build (time-out?) because an incorrect
> ’max-silent-time’ by default or because another parameter specific to
> Cuirass.

I went ahead and disabled the test suite for libmemcached in commit
9bab0950f7; the tests taking a lot of time were already marked as
expected to fail so it wasn't providing that much value to start with.

Thanks for the report!

Maxim


      reply	other threads:[~2021-03-16 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 12:18 Release 1.2.1: python2-pylibmc and libmemcached zimoun
2021-03-14  1:58 ` Maxim Cournoyer
2021-03-15  8:52   ` zimoun
2021-03-16 11:48     ` Maxim Cournoyer [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1kfqpzc.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@gnu.org \
    --cc=zimon.toutoune@gmail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.