-----Original Message-----
From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Nobuhiro Iwamatsu
Sent: Tuesday, August 4, 2020 10:54 PM
To: cip-dev@lists.cip-project.org
Cc: iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe

This recipe provides an image for testing.
If use this, it will create an image containing LTP(ltp-full), rt-tests and stress-ng.

Signed-off-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
---
recipes-core/images/cip-core-image-test.bb | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 recipes-core/images/cip-core-image-test.bb

diff --git a/recipes-core/images/cip-core-image-test.bb b/recipes-core/images/cip-core-image-test.bb
new file mode 100644
index 0000000..e2b15fc
--- /dev/null
+++ b/recipes-core/images/cip-core-image-test.bb
@@ -0,0 +1,18 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Jan Kiszka <jan.kiszka@siemens.com>
+#
+# SPDX-License-Identifier: MIT
+#
+#
+inherit dpkg-raw
+require cip-core-image.bb
+
+DESCRIPTION = "CIP Core image including test packages"
+
+IMAGE_INSTALL += "ltp-full"
+DEBIAN_DEPENDS += "rt-tests, stress-ng"
--
2.27.0

-----Original Message-----
From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
Sent: Tuesday, August 18, 2020 2:30 PM
To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe

On 18.08.20 06:57, Nobuhiro Iwamatsu wrote:

Hi Jan,

Could you comment on this patch series?

Ah, yeah, sorry.

I think now it's better to model that as extension of an image, given
that we already have two (regular + security). Or will we implicitly
test the security image via the regular one?

Jan

Best regards,
Nobuhiro

-----Original Message-----
From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Nobuhiro Iwamatsu
Sent: Tuesday, August 4, 2020 10:54 PM
To: cip-dev@lists.cip-project.org
Cc: iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe

This recipe provides an image for testing.
If use this, it will create an image containing LTP(ltp-full), rt-tests and stress-ng.

Signed-off-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
---
recipes-core/images/cip-core-image-test.bb | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 recipes-core/images/cip-core-image-test.bb

diff --git a/recipes-core/images/cip-core-image-test.bb b/recipes-core/images/cip-core-image-test.bb
new file mode 100644
index 0000000..e2b15fc
--- /dev/null
+++ b/recipes-core/images/cip-core-image-test.bb
@@ -0,0 +1,18 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Jan Kiszka <jan.kiszka@siemens.com>
+#
+# SPDX-License-Identifier: MIT
+#
+#
+inherit dpkg-raw
+require cip-core-image.bb
+
+DESCRIPTION = "CIP Core image including test packages"
+
+IMAGE_INSTALL += "ltp-full"
+DEBIAN_DEPENDS += "rt-tests, stress-ng"
--
2.27.0

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

-----Original Message-----
From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
Sent: Tuesday, August 18, 2020 10:56 PM
To: iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>; cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe

On 18.08.20 15:47, nobuhiro1.iwamatsu@toshiba.co.jp wrote:

Hi,

-----Original Message-----
From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
Sent: Tuesday, August 18, 2020 2:30 PM
To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ)

<nobuhiro1.iwamatsu@toshiba.co.jp>

Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe

On 18.08.20 06:57, Nobuhiro Iwamatsu wrote:

Hi Jan,

Could you comment on this patch series?

Ah, yeah, sorry.

I think now it's better to model that as extension of an image, given
that we already have two (regular + security). Or will we implicitly
test the security image via the regular one?

I see.
When extended, the resulting image will have the same filename as the base.
It's difficult to distinguish, so it's implemented as it is now.
If you know how to change the generated image file name by yaml file, please let me know.

Isar does not yet allow to override the image name. You'd basically have
to weaken its setting like this

[isar/meta/classes/image.bbclass]
IMAGE_FULLNAME ?= "${PN}-${DISTRO}-${MACHINE}"

and then you could override IMAGE_FULLNAME as desired.

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux