From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [RFC PATCH] testsuite: refactor
Date: Fri, 10 Dec 2021 08:14:56 +0000 [thread overview]
Message-ID: <AS4PR10MB5318FB318AC32A81A5145311ED719@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <6b9c6340-43b9-00be-9eba-14c60a01acb0@ilbers.de>
Hi Anton,
Thanks for the feedback.
Anton Mikanovich, 9. Dezember 2021 13:40:
> Test logic itself was moved to cibase to make build_test.py looks pretty
> much like the list of tests and targets.
> It makes target list maintaining much easier and avoid from searching
> though the logic if any target changes needed.
> So it's better to move existing logic from build_test.py to cibase.py,
> but not vice versa.
I get your point, although I don't fully agree.
It adds a layer of abstraction that all arguments must be passed through,
And most of the perform_* functions are only called by one test case.
But I will make another proposal, keeping the original structure.
> Moreover your patch introduce a lot of code duplication. Current
> implementation is also not ideal with it, but it's not a good idea to
> make things even worse.
The only real duplication I introduced was in the repro signed/unsigned
test, which I find hard to read (one condition "if signed", the next
"if not signed", and somehow the gpg key import happens unconditionally,
but could also be that I don't fully understand what the test wants
to do...)
> The user should be able to add any simple new test case without
> copy-pasting, but with inherit some base test classes.
>
> I also see you've reverted 94e8d23c 'CI: Fix paths for the latest
> Avocado version' which probably will not work with the latest Avocado
> versions.
That was by accident (while removing that --build switch).
Next proposal will preserve that, but rename it to --base, to make the
difference "avocado output base dir" and "bitbake build dir" clear.
Best,
Adriaan
prev parent reply other threads:[~2021-12-10 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 10:29 Adriaan Schmidt
2021-12-09 12:39 ` Anton Mikanovich
2021-12-10 8:14 ` Schmidt, Adriaan [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=AS4PR10MB5318FB318AC32A81A5145311ED719@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM \
--to=adriaan.schmidt@siemens.com \
--cc=amikan@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