From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: FYI: Feasibility of CI on github
Date: Fri, 12 Feb 2021 11:01:21 +0100 [thread overview]
Message-ID: <20210212100121.GE20742@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20210212101647.69e6b7cd@md1za8fc.ad001.siemens.net>
On Fri, Feb 12, 2021 at 10:16:47AM +0100, Henning Schild wrote:
> that is very good news. And the current CI is a total mess anyways. All
> in one 6h job. Maybe someone will find the time to improve this with
> something like bats or pytest. And rip out that Avocado stuff ... does
> anyone even use this?
We have the current testsuite in Avocado, will send patches.
The long run time is the reason why we use our own servers for CI; currently,
we get it built in 4.5 h. This could be improved to some extent through
parallelizing the test cases, but CPU and storage utilization is about 100%, so
that would require several nodes. Also, looking at the task timing diagram, it
seems that dpkg-buildpackage is completely serialized; maybe we could improve
here, too.
We did look around before introducing Avocado. Pytest is fine for module tests,
but Avocado has more infrastructure for black box and target tests that we
need. We haven't looked at bats, but I'd like stay away from shell in favor of
Python.
What I don't understand is, after we have individual test cases, how does that
help us with the long run time? Would you schedule every test case in different
steps?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2021-02-12 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 12:53 Jan Kiszka
2021-02-12 9:16 ` Henning Schild
2021-02-12 10:01 ` Baurzhan Ismagulov [this message]
2021-02-12 10:28 ` Henning Schild
2021-02-12 10:53 ` Baurzhan Ismagulov
2021-02-12 16:55 ` Jan Kiszka
2021-02-15 11:30 ` Baurzhan Ismagulov
2021-02-12 19:20 ` Henning Schild
2021-02-15 11:27 ` Baurzhan Ismagulov
2021-02-15 13:45 ` Jan Kiszka
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=20210212100121.GE20742@yssyq.m.ilbers.de \
--to=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