From: Punit Agrawal <punit1.agrawal@...>
Sent: 17 January 2020 01:02
Just thinking out loud below so please bear with me if I'm just stating
Please do ??
Chris Paterson <Chris.Paterson2@...> writes:
From: kazuhiro3.hayashi@... <kazuhiro3.hayashi@...>
Sent: 16 January 2020 06:55
Thank you for your updates!
Hello Pavel, Hayashi-san, Jan, Daniel,[...]
shown (i.e. they aren't) in LAVA due to
Currently there is an issue with the way that the cyclic test case results are
a change  made to Linaro's cyclictest.sh.
That means that the test parsing now depends on Python, which isn't
in the cip-core RFS  that is currently
being used.At the moment, we've just started creating the supported package list, so I
Do either of the CIP Core profiles include Python support?
cannot clearly say Yes.
However, at least, the both profiles can create an image including python
I think CIP-core shouldn't be thought of as a complete filesystem, but
for testingOkay. I'm thinking that we aren't going to be able to escape having a
because the python packages are already provided in upstream projects (isar,
separate 'testing' version of CIP-Core, based on ISAR on the
assumption that it has more supported packages then Deby.
Or not use CIP-Core for testing the Kernel as punit suggested ??
the base components that should exist as part of any CIP system.
As it is, it's unlikely that any real product will need only the
functionality provided by CIP core.
If that makes sense, then we should make it easy to create derived
images / filesystems that include additional software as needed for the
task at hand, e.g., testing CIP kernels.
Good point, agreed.
In addition, there is a need to test the functionality provided by the
core components, i.e., CIP-core packages along with relevant kernels on
supported devices. As yet, I don't think these tests exist (or even
This is something we do indeed need to do.
But I'm new to the project so am very likely missing things.