After bumping the release used for the aum offline upgrade branch tests
in aabc0578 to v2023.3 it became clear that this was not enough.  v2023.3
was released in November 2023, the required update to the partition
layout wasn't pushed back to the v2023 branch until March 2024. As a
result the current releases are broken.

As we now have an rc release that should contain the required fix,
switch to using this to ensure that this is indeed rectifies the issue.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We are no longer using cgroups in any special way in Apertis. In
addition it has been discovered that these tests have a flaw that allows
them to silently fail. Remove the tests as they are both broken and not
required.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Akhilesh Dandavati authored 11 months ago and Ritesh Raj Sarraf committed 10 months ago

Signed-off-by: Akhilesh Dandavati <akhilesh.dandavati@in.bosch.com>

The devices.yaml configuration has been updated so that we use v2023.3
images as a first stage in tests. For whatever reason, the image used
for the aum offline upgrade branch tests don't use this configuration,
but separate configuration in config.yaml. This is currently set to
v2022.0.

We had an issue that the RPi4 images were being produced with a smaller
boot partition than other targets. This was resulting in the space
running out on the boot partition in some tests for RPi4. This issue was
fixed, with the partitions being adjusted to be the same size as other
targets, and backported to v2024 and v2023.

We are seeing issues with the boot partition running out persisting for
the aum offline upgrade branch tests as it's using v2022 as it's first
stage image, which is no longer a supported release and as such didn't
receive the tweaks to the partition sizing.

Update the release used for this test to v2023.3 in line with other
tests.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Walter Lozano authored 11 months ago and Dylan Aïssi committed 11 months ago

There are several tests that installation additional packages to run tests, even
if this is a bad practice, and additionally requires extra space in the root
partition.

A proper fix is to rewrite the test in its own repo to only hold the important
information and binaries to run the test, but this approach requires much time.
In the meantime, at least remove unneeded dependencies to save space which is
quite limited. Also, the lack of this space in some cases can make tests to
fail, as it is not possible to install the dependencies.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 1 year ago and Dylan Aïssi committed 11 months ago

Since the functionality provided by ade has little value after the switch
to Flatpak, change the test priority to medium.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 1 year ago and Dylan Aïssi committed 11 months ago

Since the current test case uses several customizations to target device,
add additional clarifications and checks to ensure the system is properly
setup.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 1 year ago and Dylan Aïssi committed 11 months ago

Since these tests also are applicable to AMD 64 let's run them.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 1 year ago and Dylan Aïssi committed 11 months ago

This set of tests ensures that Apertis has the support for different type
of WiFi configuration. Since our OSTree image are not shipped with hostapd
enabled a set of configurations are required to properly setup the AP.

While this is possible to in OSTree images, it is easier to do it on APT
images. Moreover, the test seems to be designed to run on APT images as
it tries to create files on a read-only file system.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Balasubramanian Raju authored 1 year ago and Walter Lozano committed 11 months ago

Signed-off-by: Balasubramanian Raju <Raju.Balasubramanian@in.bosch.com>

Sudarshan CP authored 1 year ago and Walter Lozano committed 11 months ago

Signed-off-by: Sudarshan C P <sudarshan.cp2@in.bosch.com>

Sudarshan CP authored 1 year ago and Walter Lozano committed 11 months ago

Signed-off-by: Sudarshan C P <sudarshan.cp2@in.bosch.com>

This reverts commit cafe99f1.

This change makes some test to fail as they still rely on development
repos. This situation needs to be fixed before re applying this changes.

The tests that need to be moved/fixed are:

- apparmor-functional-demo (a)
- apparmor-session-lockdown-no-deny (a)
- apparmor-utils (a)

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

After moving tests to test group, the steps were updated. However, while
doing that an error was introduced and the script was not found. When
using common/run-test-in-systemd the path to the script needs to be
included, to allow the script to run. This fixes errors like

boot-no-crashes/common/tee-exec: 19: boot-no-crashes.sh: not found

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 1 year ago and Dylan Aïssi committed 1 year ago

The add repo test was used to enable development repositories which has
little value. Drop this test to avoid confusions.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 1 year ago and Dylan Aïssi committed 1 year ago

Tests should be moved to test group in gitlab, in this process move
boot-no-crashes tests.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored 1 year ago and Dylan Aïssi committed 1 year ago

Tests should be moved to test group in gitlab, in this process move
sanity tests.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Generating license BOM sometimes takes longer than an hour resulting in
jobs being killed.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

We cannot install any packages in ostree images.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

We can use busybox wget instead of curl to avoid installing extra
packages which is not possible with ostree images.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Nithin Mysore Nagesh authored 1 year ago and Walter Lozano committed 1 year ago

After systemd has started to support pstore the test needs to be adapted to use this new functionality.
Upon startup, systemd-pstore will monitor and extract the pstore contents and save it inside /var/lib/systemd/pstore/.

This also fixes the failure in the current test as /sys/fs/pstore: is not longer available.

Signed-off-by: Nithin M N <MN.Nithin@in.bosch.com>

Since package geoclue has been moved to developement it has no sense to
run it on fixed function or HMI images. The test itself passes, however,
the development repositories need to be enabled and many packages need
to be installed, which modifies the image completely.

Additionally, on HMI image, due to the number of packages that need to
be installed the LAVA job fails with

Test error: ['Unable to start test stage 1', 'Unable to start test stage 1']

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Nithin M N <MN.Nithin@in.bosch.com>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Siva Krishna Prasad Chinthalapudi authored 1 year ago and Siva Krishna Prasad Chinthalapudi committed 1 year ago

remove deprecated pkg `Xephyr` and use agl-compositor

Signed-off-by: Chinthalapudi Siva Krishna Prasad <sivakrishnaprasad.chinthalapudi@in.bosch.com>

Set image_needs_job_token when generating jobs and only pass
CI_JOB_TOKEN when it’s defined. This avoids having to work around
it when CI_JOB_TOKEN is not necessary and the job definition is used
e.g. with lava-submit/lqa which do not support "job" variable.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

To ensure the job to test ARM64 HMI images on RPI4
can be generated.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

These jobs are only used to test that the jobs can be generated
and not to generate jobs that will be sent to LAVA. The "real"
generate-tests-* jobs are located in the apertis-image-recipes
repositorty.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

These jobs are no longer used here, now they live in the
apertis-image-recipes repository. Keeping them here is
more confusing than useful.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

These tests will be used to test RPi64 images on LAVA

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Apertis v2022 is not supported anymore, instead
use the last release of Apertis v2023.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

To avoid repeating settings from image recipes, use a tiny Python script
to parse the original pipeline’s YAML definition and collect variables
into .env files to be sourced directly into the image building job’s
shell.

The original pipeline places the devroot tarball in a directory that
would otherwise not be accessible in this job, so we override it by
passing another -t devrootpack: argument to debos.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

The image building jobs are made dependencies of test jobs in order to
allow them to use freshly build image artifacts. The dependency is
marked optional to allow the pipeline to run with daily images as
before when build-custom-image: yes is not set for the package.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

While BUILD_RESULTS_URL refers to the artifact from the obs-capture job,
SOURCE_RESULTS_URL refers to the artifact from the build-source job.
To avoid capturing duplicated files on gitlab side, the debian source
package will no longer be captured by obs-capture since it's already
captured by build-source.

Moreover, for native packages, SOURCE_RESULTS_URL refers to the main
tarball instead of the *.debian.tar.* tarball which doesn't exist for
native package.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

Use lava-runner templating to pass package name instead of hardcoding it with generate*jobs.py scripts

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

To be consistent with the LAVA job which retrieve artifacts by
passing CI_JOB_TOKEN in header of curl request.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>