Re: [meta-arm] [PATCH v3] arm/trusted-firmware-rmm: Add bitbake, include and patch file for RMM

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Wed, Apr 24, 2024 at 10:18:37AM -0600, Mathieu Poirier via lists.yoctoproject.org wrote:
> On Tue, 23 Apr 2024 at 12:15, Jon Mason <jdmason@kudzu.us> wrote:
> > Please do keep abreast of the upstream changes, as I'd like for there
> > to be a CI testcase once that part is sorted out (and I'm counting on
> > you to add the CI test).
> >
> 
> Is there a documented process for CI?  I looked in the README.md, the
> documentation and CI folders but found nothing of that sort.  Due to
> their similarities, I'll start looking into what is done for Hafnium.

I had similar questions after breaking thing:

.gitlab-ci.yml and ci directories have the magic build and test matrix.

For example qemuarm64-secureboot machine build and tests are run with
this command which Ross showed me over irc:

$ kas build ci/qemuarm64-secureboot.yml:ci/testimage.yml

To debug the build and test environment you can run:

$ kas shell ci/qemuarm64-secureboot.yml:ci/testimage.yml

and then there to check how image and other variables
are formed:

$ bitbake -e core-image-base | less

To boot into the image shell manually (testimage does this automatically):

$ runqemu slirp nographic novga core-image-base

The ci/testimge.yml config runs oeqa runtime tests which
are defined TEST_SUITES variable. Tests live in
${LAYER}/lib/oeqa/runtime/cases/ as .py files, and
basically execute commands on the booted qemu target with
ssh. Often tests need additional binaries on target image
which are installed via IMAGE_INSTALL variable in kas config
files for the machine, and then test, which is part of
TEST_SUITES variable, just runs the binaries and checks
return values.

https://docs.yoctoproject.org/dev/singleindex.html#running-tests

Hope this helps,

-Mikko