Okay. I'm thinking that we aren't going to be able to escape having a separate 'testing' version of CIP-Core, based on
Do either of the CIP Core profiles include Python support?At the moment, we've just started creating the supported package list, so I
cannot clearly say Yes.
However, at least, the both profiles can create an image including python only
because the python packages are already provided in upstream projects (isar,
ISAR on the assumption that it has more supported packages then Deby.
The IRC log of yesterday: https://irclogs.baserock.org/cip/%23cip.2020-01-16.log.html
Starting from isar-cip-core would be better if we need to install
various packages for the testing like build-essential.
Deby also can generate an image including enough dependencies
of simple basic suites like LTP, cyclictest, etc. though.
Also, I guess LAVA can install additional packages for testing
(from Debian apt repository or some package directories on S3)
to their standard image after they boot on the target device.
We don't need to provide a separate testing image in this case.
Or not use CIP-Core for testing the Kernel as punit suggested ??
Personally, I would like to use CIP-Core image(s) for the kernel testing.
I have no concern about providing packages only for testing
as long as CIP is not responsible to maintain them.
Either version (thanks Daniel).
Whether CIP Core provides Python packages or not depends on
what kind of packages will be proposed (requested) by CIP WGs in future.
Currently, several packages which depend on Python packages would be
included in the next proposal from security WG (under review now).
BTW, it would be better to confirm which Python version (2.7 or 3) that
cyclictest.sh depends on.
Do you know anything about this?
Thank you for your confirmation.
Presumably we'd want to target Python 3 though if that's what the world is moving to?
I think this is one of the important topics to be discussed in CIP Core.
I agree with your idea (target on Python 3), but there are still
some packages in Debian buster that have a run-time dependency on python 2.7, unfortunately.
I would like to create another thread to think about this topic later :)
Kind regards, Chris
Linaro test-definitions  have the following tests marked within the preempt-
cyclicdeadline/cyclicdeadline.yamlbut it hasn't been merged yet and I'm not
Which of the above would be valuable to run on CIP RT Kernels?
A while back Daniel Wagner also did some work on a Jitterdebugger test ,
sure what the current status is. Any updates Daniel?the Mentor lab? Or BBB, QEMU etc.? (assuming
Is anyone able to provide RT config/defconfigs for the x86 and arm boards in
that the hardware is suitable).definitions/commit/4b5c46f275632932b3045f2ee16ad9cae5bb482d#diff-
Kind regards, Chris