From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/2] CI: install avocado in venv if host does not have it
Date: Thu, 21 Oct 2021 17:20:34 +0200 [thread overview]
Message-ID: <20211021172034.4c3a58c0@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20211021103929.GH27644@yssyq.m.ilbers.de>
Am Thu, 21 Oct 2021 12:39:30 +0200
schrieb Baurzhan Ismagulov <ibr@radix50.net>:
> On Wed, Oct 20, 2021 at 06:38:01PM +0200, Henning Schild wrote:
> > > So the fix was to pin down the version? That will cause maint
> > > headache ... quality tool and package manager!
> >
> > But thanks for the quick fix! I gave this to our gitlab to try and
> > digest. Having a testsuite is a win for sure, even if i still tend
> > to rant about the choice ... bats or pytest would have been OK as
> > well and readily available via debian.
>
> Welcome Henning,
>
> Regarding the pinning, Anton has already mentioned that we are
> analyzing the issue. The plan is to update to the latest stable
> version regularly. We still want pinning to avoid surprises, just
> like with bitbake and wic.
>
> Regarding pip, it isn't our choice :) . Debian packaging is available
> from http://deb.isar-build.org/. We have submitted Debian Policy
> updates to Avocado and are in contact with Debian developers
> regarding inclusion in upstream Debian.
The virtualenv code already assumes a debian host, so it could be
changed to in fact use that package and not a venv. That would take
care of the pinning to only one stream to deliver. Should i write a
patch?
> Regarding Avocado itself, we had discussed that in [1]. Pytest is
> good for unit testing; Avocado is more suitable for our scenarios.
> E.g., RedHat uses it for Fedora. Also, people want to migrate to
> Avocado citing flexibility limitations with pytest.
>
> All in all, I think Avocado is a good choice and is worth the hassle
> of upstreaming into Debian.
>
> 1. https://groups.google.com/g/isar-users/c/o3tJjEhe4m4/m/D7gA0SmJAQAJ
It is a chicken-egg problem. But if we want to have avocado and push
for it to become part of debian that is fine with me. Did not look into
the benefits after seeing the problems. Plus i kind of still feel the
choice was never discussed on the list, but maybe i did not follow
close enough.
I will stop the avocado-rants and focus future rants on multiconfig ;)
regards,
Henning
> With kind regards,
> Baurzhan.
>
prev parent reply other threads:[~2021-10-21 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 10:03 Anton Mikanovich
2021-10-20 10:03 ` [PATCH v2 2/2] CI: export avocado junit as gitlab report Anton Mikanovich
2021-10-20 16:11 ` Anton Mikanovich
2021-10-20 10:10 ` [PATCH v2 1/2] CI: install avocado in venv if host does not have it Anton Mikanovich
2021-10-20 16:10 ` Anton Mikanovich
2021-10-20 16:32 ` Henning Schild
2021-10-20 16:38 ` Henning Schild
2021-10-21 10:39 ` Baurzhan Ismagulov
2021-10-21 15:20 ` Henning Schild [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=20211021172034.4c3a58c0@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox