From: Loic Dachary <loic@dachary.org>
To: Zack Cerza <zack@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: teuthology gevent version
Date: Mon, 17 Nov 2014 18:33:46 +0100 [thread overview]
Message-ID: <546A317A.7010806@dachary.org> (raw)
In-Reply-To: <CAMfdg1OXa4RrmMmY8KJZRyxwuhNrRoLwq+LVZaCDZ3gOajWWMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Hi Zack,
It turns out that using a gevent threadpool was not a good idea therefore I won't pursue this lead. But I keep the answer in mind, just in case :-)
Thanks !
On 17/11/2014 18:21, Zack Cerza wrote:
> Hey Loic,
>
> I actually don't know if it would cause problems or not. It would be
> useful to do some testing with the new version: maybe create a branch
> with a patch to requirements.txt to bump the version, run the unit
> tests and then some jobs to see if things break?
>
> Thanks,
> Zack
>
> On Sun, Nov 16, 2014 at 5:04 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Zack,
>>
>> At the moment teuthology requires gevent == 0.13.6 ( https://github.com/ceph/teuthology/blob/master/requirements.txt#L2 ). Would it be a problem to upgrade to a more recent version ? I'd like to use https://github.com/gevent/gevent/blob/master/gevent/threadpool.py which was introduced in 1.0b1 http://gevent.org/changelog.html#release-1-0b1-jan-10-2012
>>
>> Cheers
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2014-11-17 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 12:04 teuthology gevent version Loic Dachary
2014-11-17 17:21 ` Zack Cerza
2014-11-17 17:33 ` Loic Dachary [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=546A317A.7010806@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=zack@redhat.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.
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.