Re: [Avocado-devel] Looking for a new name for the avocado.utils namespace

The name persea was considered a while ago wayy back when I was the project maintainer, so that would be my vote. On Fri, Mar 11, 2022 at 4:43 PM Ana Guerrero Lopez wrote: > > Hi! > > I'm working on a project to split avocado.utils and distribute it in a > separate git repository, also with a

Re: [Avocado-devel] Suggest a new maintainer

not to rely on avocado developers... Thank you > for looking into this and I'm sorry for not replying publicly. > > Regards, > Lukáš > > Dne 24. 09. 21 v 10:17 Lucas Meneghel Rodrigues napsal(a): > > Well I checked and YingShun is a member of the maintainers group: > > >

Re: [Avocado-devel] Suggest a new maintainer

M Yi Sun wrote: >> >> +1 >> >> On Thu, Sep 16, 2021 at 8:27 AM Lucas Meneghel Rodrigues >> wrote: >>> >>> You guys made a good case for YingShun. I'm onboard. >>> >>> I am on a couple of days of vacation, so if Cleber or L

Re: [Avocado-devel] Suggest a new maintainer

You guys made a good case for YingShun. I'm onboard. I am on a couple of days of vacation, so if Cleber or Lukas can grant maintainership before I have access to a computer that'll be great. Otherwise I'll do it ASAP. Thanks! On Wed, Sep 15, 2021, 5:01 AM Luyao Huang wrote: > +1 > > In my

Re: [Avocado-devel] Stalled PR's on GitHub

Ok, approved the 1st, requested changes on the 2nd. On Wed, Aug 15, 2018 at 1:42 PM Sergey Bronnikov wrote: > > Hello, > > could someone review these pull requests and commit if there is no objections? > https://github.com/avocado-framework/avocado-vt/pull/1717 >

Re: [Avocado-devel] Avocado on Wine

Nice :) I'm always impressed with what the wine guys can accomplish. And of course, avocado is keeping a tight implementation for this to be possible as well. Congrats guys! On Tue, Apr 17, 2018, 3:56 AM Cleber Rosa wrote: > I was so surprised the following worked, that I had

Re: [Avocado-devel] Request to backport PR 1376 to 36lts

On Fri, Sep 8, 2017 at 1:04 PM Amador Pahim <apa...@redhat.com> wrote: > On Fri, Sep 8, 2017 at 12:14 PM, Lucas Meneghel Rodrigues > <look...@gmail.com> wrote: > > Hi Guannan, > > > > Since 52.0 is the new LTS release, and since we usually only backport >

Re: [Avocado-devel] Request to backport PR 1376 to 36lts

Hi Guannan, Since 52.0 is the new LTS release, and since we usually only backport bugfixes, not features, I'd ask you if porting your stuff to 52.0 is an option. Because the request, as is, is something that I [1] would like to avoid. Please let me know of your current needs and let's see how we

Re: [Avocado-devel] Avocado Sprint #53 Release Meeting

Today I'm running some time sensitive errands, so I can't attend. Have a great sprint review meeting! On Mon, Aug 14, 2017 at 3:53 PM, Lukáš Doktor wrote: > Dne 11.8.2017 v 14:25 Amador Pahim napsal(a): >> Dear Avocado users and developers, >> >> I'd like to invite you all

[Avocado-devel] Inspektor 0.3.0 released

Hello folks, Considering that Cleber recently contributed support for py3 to inspektor (thank you very much, sir), I thought it was a good time to release a new upstream version. So there you go, we have inspektor 0.3.0 uploaded to pypi and tags were created appropriately on that repo. Cheers!

[Avocado-devel] Make some avocado.utils.process APIs compatible with macOS

Let's discuss this particular topic a little bit. So I dedicated some time to make avocado self tests to run on macOS (see https://github.com/avocado-framework/avocado/pull/1834). This would be a first step to make macOS (new name of what was known as Mac OS X) a 2nd tier supported platform. This

Re: [Avocado-devel] Propose Satheesh Rajendran to vt-maintainer group?

+1 On Tue, Feb 28, 2017 at 1:10 PM Yanbing Du wrote: > Hello guys, > > Recently we got some feedback that the patches from IBM do not get enough > priority, and the number of pending pull requests need to review or merge > is keep growing. Some reason is that some of our

Re: [Avocado-devel] Is anyone still using Autotest + Avocado-vt/virttest?

Porting the calls to the autotest API to avocado APIs is long overdue. With that, we can entirely drop dependency on autotest, simplifying bootstrap and deployment. On Mon, Feb 27, 2017 at 3:58 PM Lukáš Doktor wrote: > Hello guys, > > I was wondering whether anyone is still

Re: [Avocado-devel] Subprocess termination

On Mon, Feb 20, 2017 at 3:10 PM Cleber Rosa wrote: > > On 02/20/2017 08:46 AM, Andrei Stepanov wrote: > > It depends. > > > > There could be a scenario where necessary to run ~ 200 tests at once. > > If first bad-by-design test forgets/failed to cleanup, then some > >

Re: [Avocado-devel] Subprocess termination

> Radek's case is much simple: kill all children. > > > > I think it is correct behavior. This is as it should be. > > > > There is nothing to track. > > > > On opposite side, if test want to keep running process that it can > > detach it and make it daem

Re: [Avocado-devel] Subprocess termination

I would avoid keeping track of special resources by the test runner itself. It's the sort of thing that the test writer would be expected to implement on cleanup procedures. Implementing said track of subprocesses would be justifiable if we look at the following perspectives: 1) We want to

Re: [Avocado-devel] What is a right way to install avocado?

I'll try the whole setup from a virtualenv and report the results. On Fri, Feb 3, 2017 at 5:12 PM Cleber Rosa <cr...@redhat.com> wrote: > > On 02/03/2017 09:39 AM, Lucas Meneghel Rodrigues wrote: > > There is a tension between RPM being the one true way to install > >

Re: [Avocado-devel] What is a right way to install avocado?

There is a tension between RPM being the one true way to install software in Fedora, RHEL and derivatives and installing from pip, which should be convenient and portable to any distro that has virtualenv. The following use cases should be covered IMHO: 1) Full distro packages (avocado +

[Avocado-devel] aexpect 1.3.0 uploaded to pypi and builds on COPR out

I've uploaded aexpect 1.3.0 to pypi and built packages on COPR. https://pypi.python.org/pypi/aexpect/1.3.0 https://copr.fedorainfracloud.org/coprs/lmr/Autotest/build/499015/ Let me know if you have any doubts, Lucas

Re: [Avocado-devel] Docs also available now on pythonhosted.org/avocado-framework

That's a great idea. Is the upload of the docs made through ssh? On Thu, Jan 12, 2017 at 3:26 PM, Cleber Rosa wrote: > Hi folks, > > While working on "Check/Work around PIP upload failures"[1], I noticed > that the "http://pythonhosted.org/avocado-framework; URL is ours, and >

Re: [Avocado-devel] Running tests in parallel

On Wed, Nov 23, 2016 at 12:46 PM Zubair Lutfullah Kakakhel < zubair.kakak...@imgtec.com> wrote: > Hi, > > On 11/23/2016 02:28 PM, Cleber Rosa wrote: > > > > On 11/23/2016 07:07 AM, Zubair Lutfullah Kakakhel wrote: > >> Hi, > >> > >> Thank you for your comprehensive reply! > >> > >> Comments

Re: [Avocado-devel] RFC: ABRT integration

On Fri, Nov 11, 2016 at 8:21 AM Jakub Filak wrote: > Avocado developers, > > > I came across an Avocado trello card requesting integration with > systemd-coredumpctl. As a developer working on Automatic Bug Reporting Tool > (ABRT) I got interested in it. I contacted Lukas

Re: [Avocado-devel] Test assumptions question.

On Tue, Sep 13, 2016 at 10:15 AM Dmitry Monakhov wrote: > Hi, > I try to automate my kernel testing via avocado. > I've faced some general design questions. And want to ask an advice. > > Testing procedure is quite general, and suites for any project. > 1) Download source >

Re: [Avocado-devel] option --output-check-record behavior

find anything that talks about it. > > Thanks again. > > BTW, is the whole development team Brazilian? > No, we also have Lukas, from Czech republic, and also contributors in China and India. > On 09/08/2016 08:05 PM, Lucas Meneghel Rodrigues wrote: > > Yep, that was the probl