Hi guys:
As part of my effort to try to flush all my internal patches that have been
accumulating over the months, I've created a new, separate repo with my EC2
plugin, and ask whomever has time to review my code to check:
https://github.com/avocado-framework/avocado-ec2/pull/1
I tried to follow
OK, today I talked to Cleber and we figured out what was wrong. Patches
will follow.
I did test the plugin and it's working well. This first PR was merged, and
I'll work on packaging.
On Thu, Jan 28, 2016 at 1:17 AM Lucas Meneghel Rodrigues
wrote:
> Hi guys:
>
> As part of
BTW, in order for the plugin to be successfully tested, it depends on
having one patch of my PR #989:
https://github.com/lmr/avocado/commit/64694787d2825720358556379b603546361d3528
applied.
On Thu, Jan 28, 2016 at 7:28 PM Lucas Meneghel Rodrigues
wrote:
> OK, today I talked to Cleber and
+1, great stuff!
On Tue, Feb 2, 2016 at 5:51 AM Cleber Rosa wrote:
> Hi folks,
>
> I'd like to bring the following pull request to your attention:
>
> https://github.com/avocado-framework/avocado/pull/996
>
> It's titled "Safe Loader: a second, more abstract and reusable
> implementation [v0]",
Yanbing,
Avocado is tested on 2.6, the CI job runs on that platform. You are likely
lacking logutils installed (logutils==0.3.3 is what the CI job uses).
On Wed, Feb 17, 2016 at 1:33 AM Yanbing Du wrote:
> Hi Lukáš,
> Does each release will be tested on various supported python versions?
> As
OK, the thing is that Travis uses a fixed version of stevedore, and that is
why we didn't see the problem.
# stevedore for loading "new style" plugins
stevedore==1.8.0
On Wed, Feb 17, 2016 at 4:00 AM Yanbing Du wrote:
>
>
> On 02/17/2016 01:37 PM, Lucas Meneghel Rodr
You have to look into why the import test was skipped (look at the job log
to see why).
On Wed, Mar 9, 2016 at 6:17 AM Zhangbo (Oscar)
wrote:
> Hi all:
>I have successfully installed avocado-vt, and it works fine to run qemu
> tests, eg:
> avocado run io-github-autotest-qemu.boot --vt-t
> >
> >
> > Pull request maintenance - Libguestfs
> > -----
> >
> > M: Yu Mingfei
> >
> >
> > Pull request maintenance - v2v subtests
> > ---
> >
> > M: Alex Jia
> &g
I think you guys are missing the point here. I just tried Marcos's test
here and that's what I get with Avocado LTS 36.2:
$ avocado run xentest.py --output-check-record all
JOB ID : c44d95698bc6a20329691a9c10370c3b63c8944f
JOB LOG:
/home/lmr/avocado/job-results/job-2016-09-08T15.54-c44d956
By the way, you *must* set shell=True to use pipes (which I did forget).
Otherwise the pipes won't work.
On Thu, Sep 8, 2016 at 4:00 PM Lucas Meneghel Rodrigues
wrote:
> I think you guys are missing the point here. I just tried Marcos's test
> here and that's what I get
2016 at 4:01 PM Lucas Meneghel Rodrigues
wrote:
> By the way, you *must* set shell=True to use pipes (which I did forget).
> Otherwise the pipes won't work.
>
> On Thu, Sep 8, 2016 at 4:00 PM Lucas Meneghel Rodrigues
> wrote:
>
>> I think you guys are missing the
dn't 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
On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga <
marcos.matsun...@oracle.com> wrote:
> Hi guys,
>
> First of all, thanks again for your help. I really appreciate it.
>
> I found an interesting behavior. If I set loglevel=info in
> /etc/avocado/avocado.conf, it will not produce any content in
>
Too bad I was traveling and couldn't make it. I'm going to watch the video
as soon as I can.
Cheers!
On Mon, Sep 12, 2016 at 10:43 AM Amador Pahim wrote:
> Hello,
>
> Here are the links for the meeting:
>
> Hangouts: https://hangouts.google.com/call/cwyagrimv5gyrbt5muf7wdoceue
> Youtube: https:
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
> 2) configure kernel
>
On Wed, Sep 14, 2016 at 8:32 AM Marcos E. Matsunaga <
marcos.matsun...@oracle.com> wrote:
> Hi Folks,
>
> I have some questions about how avocado works.
>
> 1. If I run avocado and give it a directory that has all tests. Is there
> a way to specify the order of execution? I mean, if I name the fil
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 Doktor with a question o
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 inline
+1. Looks interesting!
On Wed, Nov 30, 2016, 12:10 PM Ademar Reis wrote:
> Saw this message on qemu-devel and I think it's a nice suggestion
> for Avocado developers.
>
> The ordering for a python project should be different, but you
> get the idea (replies to this thread with the suggested list
Although I'm not sure if github pull requests would follow this ordering
rule. If they do, the order proposed seems sane.
On Wed, Nov 30, 2016 at 5:51 PM Cleber Rosa wrote:
>
>
> On 11/30/2016 12:14 PM, Lucas Meneghel Rodrigues wrote:
> > +1. Looks interesting!
> >
I was wondering whether we could create the namespace
avocado.utils.linux, so this module would become
avocado.utils.linux.modules, or maybe even
avocado.utils.linux.drivers, to borrow a more widely known naming
convention from the Windows world. We could even move software_manager
and other linux
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
> PyPI let us host d
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
On Wed, Jan 25, 2017 at 6:44 AM Adil Kamal wrote:
> Hello,
>
> Please confirm if avocado (and more particularly avocado-vt) is supported
> for Ubuntu in general, and Ubuntu 14.04 in specific. I am able to install
> avocado with some plugin errors though, however can not get avocado-vt to
> instal
Isn't catching the exception and checking if its fields look like what you
expect an option? That is the sort of thing that in my mind wouldn't need
additional support.
On Tue, Jan 24, 2017 at 4:33 PM Radek Duda wrote:
> Hi,
>
> I wonder if there is any possiblity to perform negative testcases i
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-v
I'll try the whole setup from a virtualenv and report the results.
On Fri, Feb 3, 2017 at 5:12 PM Cleber Rosa 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
> > software in Fedora, R
I'm not sure putting a file with references to a relatively independent
plugin in the main avocado repo the correct thing to do. It's probably
better to put a file with that summary in the avocado-vt repository instead.
On Tue, Feb 7, 2017 at 12:19 PM Andrei Stepanov wrote:
> Hi,
>
> How do you
Or maybe adapt the text and split the files, one that goes into avocado.git
and another one that goes into avocado-vt.git.
On Tue, Feb 7, 2017 at 12:46 PM Lucas Meneghel Rodrigues
wrote:
> I'm not sure putting a file with references to a relatively independent
> plugin in the main a
On Fri, Feb 10, 2017 at 11:16 AM Cleber Rosa wrote:
>
>
> On 02/10/2017 05:01 AM, Andrei Stepanov wrote:
> > Hi.
> >
> > We need a reliable mechanism to notify Beaker server about start+result
> > of a avocado-vt test. As you know, avocado-vt test is one of the many
> > tests produced from cartes
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 reduce
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 daemon.
> >
As an example, I wrote scylla-cluster-tests
https://github.com/scylladb/scylla-cluster-tests/
This test suite creates instances and storages on cloud providers, such as
AWS. Those resources cost money, so making sure stray instances are
properly terminated is paramount. There are cleanup procedur
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
> > sequential tests also will f
Now that of course doesn't solve the problem I had with
scylla-cluster-tests, since the resources being used are external to the
machine executing tests. For cases like that, I'm afraid only good test
development practices can help.
On Mon, Feb 20, 2017 at 3:21 PM Lucas Meneghel Rodrig
+1
On Thu, Feb 23, 2017, 11:50 AM Lukáš Doktor wrote:
> Hello guys,
>
> I see an increasing tension between tp-spice guys and the rest of
> avocado-vt guys because some of their patches do not get enough
> priority. Currently there is no maintainer from tp-spice group so to
> improve the situati
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 using Autotest to run
+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 maintainers are now focu
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
Hi guys,
After some discussion on the subject, we decided to move aexpect and
inspektor from their original homes in github.io/autotest to
github.io/avocado. Github is kind enough to provide redirection from one
domain to another, so users shouldn't be impacted. However, I would
recommend that fro
On Wed, Mar 22, 2017 at 7:05 PM Lukáš Doktor wrote:
> Hello guys,
>
> I remember early in development we decided to abort the execution when
> `setUp` fails without executing `tearDown`, but over the time I keep
> thinking about it and I don't think it's optimal. My main reason is to
> simplify `
Hi guys,
Just passing by to let you know aexpect 1.4.0 was released. This release
contains one bugfix by Lukas and a new spec file package name, courtesy of
Cleber. Pypi and spec files were properly updated.
Cheers!
Lucas
Some quick thoughts about what you could do (points 1 and 2, other
paragraphs are more thoughts on making avocado better for such cases):
1) For the cases using unittest, you could try to import avocado, if it
fails, fall back to unittest.TestCase, such as
try:
from avocado import Test as Tes
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!
My 2 cents, I agree with Cleber here 100%. The current docstring tags are
more of a workaround, and ideally none of that would be necessary, and it's
worth to spend more time trying to get rid of it.
About using only AST static analysis, this is the one reason why the
docstring tags are being used
+1
On Fri, Aug 4, 2017 at 1:28 PM Guannan Sun wrote:
> Hi,
>
> As people change in team, new maintainers required for step up on
> maintaining avocado-vt/tp-libvirt projects. As tp-libvirt is still growing,
> you could find data from past 8 months:
>
>
> https://github.com/autotest/tp-libvirt/gr
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 to a sprint release an
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
On Fri, Sep 8, 2017 at 1:04 PM Amador Pahim wrote:
> On Fri, Sep 8, 2017 at 12:14 PM, Lucas Meneghel Rodrigues
> wrote:
> > Hi Guannan,
> >
> > Since 52.0 is the new LTS release, and since we usually only backport
> > bugfixes, not features, I'd ask you
On Mon, Sep 11, 2017 at 10:23 AM Lukáš Doktor wrote:
> Hello Guannan,
>
> theoretically we should not accept such backport, because it's a new
> feature, not a bugfix. Anyway it touches `avocado.utils` and it's not
> changing existing callbacks. What do you think, guys? In my view the
> `avocado/
On Wed, Nov 8, 2017 at 4:01 PM, Cleber Rosa wrote:
> Hi everyone,
>
> This is kind of brainstorm about the really annoying issue we've trying
> to deal with in Avocado. The root problem we're trying to fix is that
> Avocado's "output check" feature can not be used when the test's
> generated cont
+1
On Fri, Mar 2, 2018 at 10:53 AM, Chunfu Wen wrote:
> Hi All,
>
> Thank Kyla for thumbing up!
> By the way,some contribution details follow as:
> 1)PR reviewed by me (dated from Aug 30, 2017):50,reference link: [1]
> 2)PR submitted by me:7,reference link:[2]
>
> Best Regards,
>
> Chunfu Wen
>
>
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 to share it:
>
> --
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
> https://github.com/avocado-framewo
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 opin
25 AM 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 Cl
t 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:
> >
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 di
58 matches
Mail list logo
