public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: <isar-users@googlegroups.com>, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v2 1/2] CI: install avocado in venv if host does not have it
Date: Wed, 20 Oct 2021 18:38:01 +0200	[thread overview]
Message-ID: <20211020183801.37ab4b03@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20211020183237.60a819bc@md1za8fc.ad001.siemens.net>

Am Wed, 20 Oct 2021 18:32:37 +0200
schrieb Henning Schild <henning.schild@siemens.com>:

> Am Wed, 20 Oct 2021 19:10:48 +0300
> schrieb Anton Mikanovich <amikan@ilbers.de>:
> 
> > On 20.10.21 13:03, Anton Mikanovich wrote:  
> > > From: Henning Schild <henning.schild@siemens.com>
> > >
> > > Avocado packages are currently not available in Debian. Use
> > > virtualenv and pip for sites that do not provide avocado as part
> > > of execution environment. We expect the execution environment to
> > > be Debian-based and to allow us to sudo (true for kas-isar
> > > container).
> > >
> > > Use version 88.0 as the latest working one from pip.
> > >
> > > Signed-off-by: Henning Schild <henning.schild@siemens.com>
> > > Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> > > ---
> > >   scripts/ci_build.sh | 11 +++++++++++
> > >   1 file changed, 11 insertions(+)
> > >
> > > diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
> > > index 4534957..32054c4 100755
> > > --- a/scripts/ci_build.sh
> > > +++ b/scripts/ci_build.sh
> > > @@ -14,6 +14,17 @@ export PATH=$PATH:/sbin
> > >   # Go to Isar root
> > >   cd "$(dirname "$0")/.."
> > >   
> > > +# install avocado in virtualenv in case it is not there already
> > > +if ! command -v avocado > /dev/null; then
> > > +    sudo apt-get update -qq
> > > +    sudo apt-get install -y virtualenv
> > > +    rm -rf /tmp/avocado_venv
> > > +    virtualenv --python python3 /tmp/avocado_venv
> > > +    source /tmp/avocado_venv/bin/activate
> > > +    # The latest working version of Avocado framework
> > > +    pip install avocado-framework==88.0
> > > +fi
> > > +
> > >   # Get Avocado build tests path
> > >   BUILD_TEST_DIR="$(pwd)/testsuite/build_test"
> > >       
> > 
> > Applied to next.  
> 
> 
> 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.

Henning

> Henning
> 


  reply	other threads:[~2021-10-20 16:38 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 [this message]
2021-10-21 10:39       ` Baurzhan Ismagulov
2021-10-21 15:20         ` Henning Schild

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=20211020183801.37ab4b03@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=ibr@ilbers.de \
    --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