[xenomai-images][PATCH 0/6] Update to Debian 11

[xenomai-images][PATCH 0/6] Update to Debian 11

[Florian Bezdeka]

Hi all,

with this series the Xenomai demo image will be based on Debian 11.

All Debian 11 related topics that had to be adressed are now merged to
the Xenomai next branch. The stable branches have not yet been updated
so CI will report some failures for such branches.

Patch 4 made it to the list but has not been applied to next yet. That's
why I resend it, integrated into this series at the right place.

The Xenomai LAVA instance has been down while working on this topic. The
job submission to LAVA failed, but the test jobs where still marked as
successful. That is now fixed as well.

Best regards,
Florian

Florian Bezdeka (5):
  ci: Introduce kas option file for CI builds
  kas: Integrate opt-debug.yml into opt-ci.yml
  demo-image: Fix sshd-regen-keys problems on arm / qemu
  xenomai-demo: Switch to Debian bullseye
  ci: Fail test job when an error occurred during lava job submission

Jan Kiszka (1):
  linux-xenomai: arm: Enable CONFIG_ARM_MODULE_PLTS

 ci/gitlab-ci-base.yml                         |  4 +-
 conf/distro/xenomai-demo.conf                 |  4 +-
 ...Start-key-generation-after-entropy-s.patch | 40 +++++++++++++++++++
 ...Fix-some-systemd-obsolete-warnings-a.patch | 34 ++++++++++++++++
 isar-patches/series                           |  2 +
 kas.yml                                       |  4 ++
 opt-ci.yml                                    | 21 ++++++++++
 recipes-kernel/linux/files/armhf_defconfig    |  1 -
 scripts/run-lava-tests.sh                     |  1 +
 9 files changed, 106 insertions(+), 5 deletions(-)
 create mode 100644 isar-patches/0001-sshd-regen-keys-Start-key-generation-after-entropy-s.patch
 create mode 100644 isar-patches/0002-sshd-regen-keys-Fix-some-systemd-obsolete-warnings-a.patch
 create mode 100644 isar-patches/series
 create mode 100644 opt-ci.yml

-- 
2.31.1

[xenomai-images][PATCH 1/6] ci: Introduce kas option file for CI builds

[Florian Bezdeka]

For now the difference between the demo and the "ci image" is:
 - Removed sshd-regen-keys: Reduces the (first) boot time especially on
   low end CI hardware. Helps to stay within LAVA timeouts.

 - Removed expand-on-first-boot: Doesn't make much sense on CI runs as
   we don't really use the filesystem. Helps to reduce the first boot
   time a bit.

CI builds will now use that file.

Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
 ci/gitlab-ci-base.yml |  4 ++--
 opt-ci.yml            | 19 +++++++++++++++++++
 2 files changed, 21 insertions(+), 2 deletions(-)
 create mode 100644 opt-ci.yml

diff --git a/ci/gitlab-ci-base.yml b/ci/gitlab-ci-base.yml
index 8a1dbfb..26c3f60 100644
--- a/ci/gitlab-ci-base.yml
+++ b/ci/gitlab-ci-base.yml
@@ -39,8 +39,8 @@ default:
   stage: build
   script:
     - sudo sh -c "echo 'nameserver 8.8.8.8' > /etc/resolv.conf"
-    - echo "Building kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml"
-    - kas build kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml
+    - echo "Building kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml:opt-ci.yml"
+    - kas build kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml:opt-ci.yml
     - if [ -n "${USE_S3_BUCKET}" ]; then scripts/deploy_to_aws.sh ${TARGET}; fi
 
 .test:
diff --git a/opt-ci.yml b/opt-ci.yml
new file mode 100644
index 0000000..6766cb0
--- /dev/null
+++ b/opt-ci.yml
@@ -0,0 +1,19 @@
+#
+# Xenomai Real-Time System
+#
+# Copyright (c) Siemens AG, 2021
+#
+# Authors:
+#  Florian Bezdeka <florian.bezdeka@siemens.com>
+#
+# SPDX-License-Identifier: MIT
+#
+
+header:
+  version: 10
+
+local_conf_header:
+  xenomai-ci: |
+    ROOTFS_POSTPROCESS_COMMAND_remove = "image_postprocess_sshd_key_regen"
+    IMAGE_INSTALL_remove += "sshd-regen-keys"
+    IMAGE_INSTALL_remove += "expand-on-first-boot"
\ No newline at end of file
-- 
2.31.1

[xenomai-images][PATCH 2/6] kas: Integrate opt-debug.yml into opt-ci.yml

[Florian Bezdeka]

Whenever the kas option file opt-ci.yml is used we want the same build
options as the CI does, which includes setting the debug options.

Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
 ci/gitlab-ci-base.yml | 4 ++--
 opt-ci.yml            | 2 ++
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/ci/gitlab-ci-base.yml b/ci/gitlab-ci-base.yml
index 26c3f60..3378fcf 100644
--- a/ci/gitlab-ci-base.yml
+++ b/ci/gitlab-ci-base.yml
@@ -39,8 +39,8 @@ default:
   stage: build
   script:
     - sudo sh -c "echo 'nameserver 8.8.8.8' > /etc/resolv.conf"
-    - echo "Building kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml:opt-ci.yml"
-    - kas build kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml:opt-ci.yml
+    - echo "Building kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-ci.yml"
+    - kas build kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-ci.yml
     - if [ -n "${USE_S3_BUCKET}" ]; then scripts/deploy_to_aws.sh ${TARGET}; fi
 
 .test:
diff --git a/opt-ci.yml b/opt-ci.yml
index 6766cb0..663a908 100644
--- a/opt-ci.yml
+++ b/opt-ci.yml
@@ -11,6 +11,8 @@
 
 header:
   version: 10
+  includes:
+    - opt-debug.yml
 
 local_conf_header:
   xenomai-ci: |
-- 
2.31.1

[xenomai-images][PATCH 3/6] demo-image: Fix sshd-regen-keys problems on arm / qemu

[Florian Bezdeka]

See patch descriptions for details. The main problem was that the key
generation took extremly long and several other services (like the
serial consoles) were not started because the configured timeout was
reached.

Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
 ...Start-key-generation-after-entropy-s.patch | 40 +++++++++++++++++++
 ...Fix-some-systemd-obsolete-warnings-a.patch | 34 ++++++++++++++++
 isar-patches/series                           |  2 +
 kas.yml                                       |  4 ++
 4 files changed, 80 insertions(+)
 create mode 100644 isar-patches/0001-sshd-regen-keys-Start-key-generation-after-entropy-s.patch
 create mode 100644 isar-patches/0002-sshd-regen-keys-Fix-some-systemd-obsolete-warnings-a.patch
 create mode 100644 isar-patches/series

diff --git a/isar-patches/0001-sshd-regen-keys-Start-key-generation-after-entropy-s.patch b/isar-patches/0001-sshd-regen-keys-Start-key-generation-after-entropy-s.patch
new file mode 100644
index 0000000..56fb7d6
--- /dev/null
+++ b/isar-patches/0001-sshd-regen-keys-Start-key-generation-after-entropy-s.patch
@@ -0,0 +1,40 @@
+From 94b24ec5be3e3b0d32db4dbfe7cc9b63d8a0ce0a Mon Sep 17 00:00:00 2001
+From: Florian Bezdeka <florian.bezdeka@siemens.com>
+Date: Thu, 7 Oct 2021 17:59:44 +0200
+Subject: [PATCH 1/2] sshd-regen-keys: Start key generation after entropy seed
+
+Especially on low-end systems (including arm on qemu) it could happen
+that the key generation took extremly long. As side effect some other
+services (like the ones for serial consoles) run into the configured
+timeouts.
+
+[ TIME ] Timed out waiting for device /dev/hvc0.
+[DEPEND] Dependency failed for Serial Getty on hvc0.
+[ TIME ] Timed out waiting for device /dev/ttyAMA0.
+[DEPEND] Dependency failed for Serial Getty on ttyAMA0.
+
+Delaying the key generation to the point in time where
+systemd-random-seed finished solves this problem. My current
+understanding is that the regeneration is waiting for enough entropy
+which is being seeded in parallel.
+
+Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
+---
+ .../sshd-regen-keys/files/sshd-regen-keys.service                | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
+index a05e1a9..4d0a8c6 100644
+--- a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
++++ b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
+@@ -3,6 +3,7 @@ Description=Regenerate sshd host keys
+ DefaultDependencies=no
+ Conflicts=shutdown.target
+ After=systemd-remount-fs.service
++After=systemd-random-seed.service
+ Before=shutdown.target sshd.service
+ ConditionPathIsReadWrite=/etc
+ 
+-- 
+2.31.1
+
diff --git a/isar-patches/0002-sshd-regen-keys-Fix-some-systemd-obsolete-warnings-a.patch b/isar-patches/0002-sshd-regen-keys-Fix-some-systemd-obsolete-warnings-a.patch
new file mode 100644
index 0000000..1b8d2e0
--- /dev/null
+++ b/isar-patches/0002-sshd-regen-keys-Fix-some-systemd-obsolete-warnings-a.patch
@@ -0,0 +1,34 @@
+From 4d20f39987326d1a545015c9bbb385b6d9219c67 Mon Sep 17 00:00:00 2001
+From: Florian Bezdeka <florian.bezdeka@siemens.com>
+Date: Thu, 7 Oct 2021 18:05:15 +0200
+Subject: [PATCH 2/2] sshd-regen-keys: Fix some systemd obsolete warnings about
+ using syslog
+
+Fixes the following warnings:
+
+[   11.450104] systemd[1]: /lib/systemd/system/sshd-regen-keys.service:15:
+[   11.450806] systemd[1]: /lib/systemd/system/sshd-regen-keys.service:16:
+	Standard output type syslog is obsolete, automatically updating to journal.
+	Please update your unit file, and consider removing the setting altogether.
+
+Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
+---
+ .../sshd-regen-keys/files/sshd-regen-keys.service               | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
+index 4d0a8c6..ebcee86 100644
+--- a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
++++ b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
+@@ -13,8 +13,6 @@ RemainAfterExit=yes
+ Environment=DEBIAN_FRONTEND=noninteractive
+ ExecStart=/usr/sbin/sshd-regen-keys.sh
+ ExecStartPost=-/bin/systemctl disable sshd-regen-keys.service
+-StandardOutput=syslog
+-StandardError=syslog
+ 
+ [Install]
+ WantedBy=sysinit.target
+-- 
+2.31.1
+
diff --git a/isar-patches/series b/isar-patches/series
new file mode 100644
index 0000000..3e76460
--- /dev/null
+++ b/isar-patches/series
@@ -0,0 +1,2 @@
+0001-sshd-regen-keys-Start-key-generation-after-entropy-s.patch
+0002-sshd-regen-keys-Fix-some-systemd-obsolete-warnings-a.patch
diff --git a/kas.yml b/kas.yml
index c8bafcd..345fccc 100644
--- a/kas.yml
+++ b/kas.yml
@@ -23,6 +23,10 @@ repos:
   isar:
     url: https://github.com/ilbers/isar.git
     refspec: 1cfe166c5e53ae96bc07b895a92bf6cd7ace7bc9
+    patches:
+      "isar-patches":
+        repo: xenomai
+        path: isar-patches
     layers:
       meta:
 
-- 
2.31.1

[xenomai-images][PATCH 4/6] linux-xenomai: arm: Enable CONFIG_ARM_MODULE_PLTS

[Florian Bezdeka]

From: Jan Kiszka <jan.kiszka@siemens.com>

No reason to turn this off, in fact, we have to turn it on with
bullseye's gcc-10 and debug options enabled to avoid relocation
range problems when loading modules.

Reported-by: Florian Bezdeka <florian.bezdeka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 recipes-kernel/linux/files/armhf_defconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/recipes-kernel/linux/files/armhf_defconfig b/recipes-kernel/linux/files/armhf_defconfig
index ef4981d..eda674c 100644
--- a/recipes-kernel/linux/files/armhf_defconfig
+++ b/recipes-kernel/linux/files/armhf_defconfig
@@ -1112,7 +1112,6 @@ CONFIG_HIGHPTE=y
 CONFIG_CPU_SW_DOMAIN_PAN=y
 CONFIG_HW_PERF_EVENTS=y
 CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
-# CONFIG_ARM_MODULE_PLTS is not set
 CONFIG_FLATMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
 CONFIG_HAVE_MEMBLOCK=y
-- 
2.31.1

[xenomai-images][PATCH 5/6] xenomai-demo: Switch to Debian bullseye

[Florian Bezdeka]

Switching from Debian buster to Debian bullseye as base for or xenomai-demo
distribution.

Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
 conf/distro/xenomai-demo.conf | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/conf/distro/xenomai-demo.conf b/conf/distro/xenomai-demo.conf
index 1c9209d..4794584 100644
--- a/conf/distro/xenomai-demo.conf
+++ b/conf/distro/xenomai-demo.conf
@@ -9,12 +9,12 @@
 # SPDX-License-Identifier: MIT
 #
 
-require conf/distro/debian-buster.conf
+require conf/distro/debian-bullseye.conf
 
 PREFERRED_VERSION_xenomai ?= "3.1%"
 include conf/distro/include/xenomai-version.inc
 
-HOST_DISTRO ?= "debian-buster"
+HOST_DISTRO ?= "debian-bullseye"
 
 KERNEL_NAME = "xenomai"
 
-- 
2.31.1

[xenomai-images][PATCH 6/6] ci: Fail test job when an error occurred during lava job submission

[Florian Bezdeka]

It can happen that the LAVA job submission fails. If so, the CI job
should be marked as failed. Previously we had something like the
following in the log, but the job was still marked as "OK".

Log:
connect to lava server: https://lava.xenomai.org
Deploy artifacts from 'https://xenomai-images-artifacts.s3.amazonaws.com/artifacts'
submit lava job
<ProtocolError for https://[snip]/RPC2: 500 HTTPSConnectionPool(host='lava.xenomai.org', port=443): Read timed out. (read timeout=20.0)>
<ProtocolError for https://[snip]/RPC2: 500 HTTPSConnectionPool(host='lava.xenomai.org', port=443): Read timed out. (read timeout=20.0)>
scripts/run-lava-tests.sh: 56: [: Illegal number:

Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
 scripts/run-lava-tests.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/run-lava-tests.sh b/scripts/run-lava-tests.sh
index dde542c..de63b28 100755
--- a/scripts/run-lava-tests.sh
+++ b/scripts/run-lava-tests.sh
@@ -9,6 +9,7 @@
 #
 # SPDX-License-Identifier: MIT
 #
+set -e
 TARGET=$1
 if [ -z "${TARGET}" ]; then
     echo "no target was given"
-- 
2.31.1

Re: [xenomai-images][PATCH 1/6] ci: Introduce kas option file for CI builds

[Jan Kiszka]

On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
> For now the difference between the demo and the "ci image" is:
>  - Removed sshd-regen-keys: Reduces the (first) boot time especially on
>    low end CI hardware. Helps to stay within LAVA timeouts.

opt-lava-test.yml?

> 
>  - Removed expand-on-first-boot: Doesn't make much sense on CI runs as
>    we don't really use the filesystem. Helps to reduce the first boot
>    time a bit.

That should rather be attached to the image format. If building lava
(opt-lava-test.yml) or qemu (opt-ext4-gz.yml), it does not make sense
and should go.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: [xenomai-images][PATCH 6/6] ci: Fail test job when an error occurred during lava job submission

[Jan Kiszka]

On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
> It can happen that the LAVA job submission fails. If so, the CI job
> should be marked as failed. Previously we had something like the
> following in the log, but the job was still marked as "OK".
> 
> Log:
> connect to lava server: https://lava.xenomai.org
> Deploy artifacts from 'https://xenomai-images-artifacts.s3.amazonaws.com/artifacts'
> submit lava job
> <ProtocolError for https://[snip]/RPC2: 500 HTTPSConnectionPool(host='lava.xenomai.org', port=443): Read timed out. (read timeout=20.0)>
> <ProtocolError for https://[snip]/RPC2: 500 HTTPSConnectionPool(host='lava.xenomai.org', port=443): Read timed out. (read timeout=20.0)>
> scripts/run-lava-tests.sh: 56: [: Illegal number:
> 
> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
> ---
>  scripts/run-lava-tests.sh | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/scripts/run-lava-tests.sh b/scripts/run-lava-tests.sh
> index dde542c..de63b28 100755
> --- a/scripts/run-lava-tests.sh
> +++ b/scripts/run-lava-tests.sh
> @@ -9,6 +9,7 @@
>  #
>  # SPDX-License-Identifier: MIT
>  #
> +set -e
>  TARGET=$1
>  if [ -z "${TARGET}" ]; then
>      echo "no target was given"
> 

Is this resolving what we saw with lava.xenomai.org being down?

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: [xenomai-images][PATCH 1/6] ci: Introduce kas option file for CI builds

[Florian Bezdeka]

On 13.10.21 09:26, Jan Kiszka wrote:
> On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
>> For now the difference between the demo and the "ci image" is:
>>  - Removed sshd-regen-keys: Reduces the (first) boot time especially on
>>    low end CI hardware. Helps to stay within LAVA timeouts.
> 
> opt-lava-test.yml?

I tried to avoid "product" names like LAVA. So it's opt-test.yml vs.
opt-ci.yml. Which one do you prefer?

> 
>>
>>  - Removed expand-on-first-boot: Doesn't make much sense on CI runs as
>>    we don't really use the filesystem. Helps to reduce the first boot
>>    time a bit.
> 
> That should rather be attached to the image format. If building lava
> (opt-lava-test.yml) or qemu (opt-ext4-gz.yml), it does not make sense
> and should go.

That makes sense. Will do.

> 
> Jan
> 


-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: [xenomai-images][PATCH 6/6] ci: Fail test job when an error occurred during lava job submission

[Florian Bezdeka]

On 13.10.21 09:28, Jan Kiszka wrote:
> On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
>> It can happen that the LAVA job submission fails. If so, the CI job
>> should be marked as failed. Previously we had something like the
>> following in the log, but the job was still marked as "OK".
>>
>> Log:
>> connect to lava server: https://lava.xenomai.org
>> Deploy artifacts from 'https://xenomai-images-artifacts.s3.amazonaws.com/artifacts'
>> submit lava job
>> <ProtocolError for https://[snip]/RPC2: 500 HTTPSConnectionPool(host='lava.xenomai.org', port=443): Read timed out. (read timeout=20.0)>
>> <ProtocolError for https://[snip]/RPC2: 500 HTTPSConnectionPool(host='lava.xenomai.org', port=443): Read timed out. (read timeout=20.0)>
>> scripts/run-lava-tests.sh: 56: [: Illegal number:
>>
>> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
>> ---
>>  scripts/run-lava-tests.sh | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/scripts/run-lava-tests.sh b/scripts/run-lava-tests.sh
>> index dde542c..de63b28 100755
>> --- a/scripts/run-lava-tests.sh
>> +++ b/scripts/run-lava-tests.sh
>> @@ -9,6 +9,7 @@
>>  #
>>  # SPDX-License-Identifier: MIT
>>  #
>> +set -e
>>  TARGET=$1
>>  if [ -z "${TARGET}" ]; then
>>      echo "no target was given"
>>
> 
> Is this resolving what we saw with lava.xenomai.org being down?

Yes. See cover letter ;-)

> 
> Jan
> 


-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: [xenomai-images][PATCH 1/6] ci: Introduce kas option file for CI builds

[Florian Bezdeka]

On 13.10.21 09:50, Florian Bezdeka via Xenomai wrote:
> On 13.10.21 09:26, Jan Kiszka wrote:
>> On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
>>> For now the difference between the demo and the "ci image" is:
>>>  - Removed sshd-regen-keys: Reduces the (first) boot time especially on
>>>    low end CI hardware. Helps to stay within LAVA timeouts.
>>
>> opt-lava-test.yml?
> 
> I tried to avoid "product" names like LAVA. So it's opt-test.yml vs.
> opt-ci.yml. Which one do you prefer?
> 
>>
>>>
>>>  - Removed expand-on-first-boot: Doesn't make much sense on CI runs as
>>>    we don't really use the filesystem. Helps to reduce the first boot
>>>    time a bit.
>>
>> That should rather be attached to the image format. If building lava
>> (opt-lava-test.yml) or qemu (opt-ext4-gz.yml), it does not make sense
>> and should go.
> 
> That makes sense. Will do.
> 

Already done. The qemu machine config already has it. So the only place
where we need it is for CI / test boards, which is opt-ci.yml or
opt-test.yml.

>>
>> Jan
>>
> 
> 


-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: [xenomai-images][PATCH 1/6] ci: Introduce kas option file for CI builds

[Florian Bezdeka]

On 13.10.21 09:50, Florian Bezdeka via Xenomai wrote:
> On 13.10.21 09:26, Jan Kiszka wrote:
>> On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
>>> For now the difference between the demo and the "ci image" is:
>>>  - Removed sshd-regen-keys: Reduces the (first) boot time especially on
>>>    low end CI hardware. Helps to stay within LAVA timeouts.
>>
>> opt-lava-test.yml?
> 
> I tried to avoid "product" names like LAVA. So it's opt-test.yml vs.
> opt-ci.yml. Which one do you prefer?
> 
>>
>>>
>>>  - Removed expand-on-first-boot: Doesn't make much sense on CI runs as
>>>    we don't really use the filesystem. Helps to reduce the first boot
>>>    time a bit.
>>
>> That should rather be attached to the image format. If building lava
>> (opt-lava-test.yml) or qemu (opt-ext4-gz.yml), it does not make sense
>> and should go.
> 
> That makes sense. Will do.
> 

Already done. The qemu machine config already has it. So the only place
where we need it is for CI / test boards, which is opt-ci.yml or
opt-test.yml.

>>
>> Jan
>>
> 
> 

Re: [xenomai-images][PATCH 1/6] ci: Introduce kas option file for CI builds

[Jan Kiszka]

On 13.10.21 09:50, Florian Bezdeka wrote:
> On 13.10.21 09:26, Jan Kiszka wrote:
>> On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
>>> For now the difference between the demo and the "ci image" is:
>>>  - Removed sshd-regen-keys: Reduces the (first) boot time especially on
>>>    low end CI hardware. Helps to stay within LAVA timeouts.
>>
>> opt-lava-test.yml?
> 
> I tried to avoid "product" names like LAVA. So it's opt-test.yml vs.
> opt-ci.yml. Which one do you prefer?
> 

We already have opt-lava-test.yml. Renaming it would be a different patch.

Jan

>>
>>>
>>>  - Removed expand-on-first-boot: Doesn't make much sense on CI runs as
>>>    we don't really use the filesystem. Helps to reduce the first boot
>>>    time a bit.
>>
>> That should rather be attached to the image format. If building lava
>> (opt-lava-test.yml) or qemu (opt-ext4-gz.yml), it does not make sense
>> and should go.
> 
> That makes sense. Will do.
> 
>>
>> Jan
>>
> 
> 


-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: [xenomai-images][PATCH 1/6] ci: Introduce kas option file for CI builds

[Florian Bezdeka]

On 13.10.21 10:08, Jan Kiszka wrote:
> On 13.10.21 09:50, Florian Bezdeka wrote:
>> On 13.10.21 09:26, Jan Kiszka wrote:
>>> On 13.10.21 09:18, Florian Bezdeka via Xenomai wrote:
>>>> For now the difference between the demo and the "ci image" is:
>>>>  - Removed sshd-regen-keys: Reduces the (first) boot time especially on
>>>>    low end CI hardware. Helps to stay within LAVA timeouts.
>>>
>>> opt-lava-test.yml?
>>
>> I tried to avoid "product" names like LAVA. So it's opt-test.yml vs.
>> opt-ci.yml. Which one do you prefer?
>>
> 
> We already have opt-lava-test.yml. Renaming it would be a different patch.

Ha, I see... This one is actually used inconsistently for real boards
only, so not for all lava-tests what the name would indicate. Let me see
if I can clean that up.

> 
> Jan
> 
>>>
>>>>
>>>>  - Removed expand-on-first-boot: Doesn't make much sense on CI runs as
>>>>    we don't really use the filesystem. Helps to reduce the first boot
>>>>    time a bit.
>>>
>>> That should rather be attached to the image format. If building lava
>>> (opt-lava-test.yml) or qemu (opt-ext4-gz.yml), it does not make sense
>>> and should go.
>>
>> That makes sense. Will do.
>>
>>>
>>> Jan
>>>
>>
>>
> 
>