As explained in f2100830 RPi4 had a different layout with not enough space
to perform kernel updates. Unfortunately this was properly fixed after the
release of v2023.5 so, to in order to perform the test use a different image
which has been published only for this purpose, which is based on v2023.5
but with the new layout.

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

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

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>

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>

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>

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>

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>

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

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>

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>

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

In order to retrieve artifacts from private gitlab projects,
we need to pass the gitlab CI_JOB_TOKEN as header to curl
otherwise access is not granted.

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

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
Signed-off-by: Malik Mlitat <malik.mlitat@de.bosch.com>

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

Walter Lozano authored 1 year ago and Sjoerd Simons committed 1 year ago

During the branching the NFS URL for R-Car was tweaked, causing the tests
to fail. Fix the NFS URL.

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

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

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

Switch to the new R-Car r8a779m1-ulcb device type as it is the new
reference board for this release.

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

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

This test relies in a Debian LXC image to be deployed in the DUT which
presents a problem in some scenarios, devices requires access to public
Internet and QEMU requires LXC support.

Disable this test until a it is reimplemented to overcome the current
limitations.

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

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

Signed-off-by: Andre Moreira Magalhaes <andre.magalhaes@collabora.com>

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

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

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

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

The group template was created after
9dc1fafa was merged, which removed all
instances of the 'name:' key. However, this turned out to break test
submission, which is why it was then reverted in
79a2b0df.

Unfortunately, I did not realize that the new IoT group was missing
this field, which means that 'name:' was never added back there and IoT
image test submission is broken.

https://phabricator.apertis.org/T8949



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

The tests need credentials to be passed to them, so a new LAVA group is
created that passes them down to the scripts. In order to avoid any
leakage, visibility controls are added to the job generation, so that
the IoT jobs can set the visibility to be internal-only.

https://phabricator.apertis.org/T8949



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

qa.apertis.org is being served by the qa-report-app.
So modify the LAVA callback to point to qa.apertis.org.

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

This reverts commit 0f2e8a1a.

On commit 0f2e8a1a a clean up was introduced to remove validation warnings.
Unfortunately the tool prompts is key is used by lava to detect when the
deploy action has finished when the tool is different from dd as described
in:

https://github.com/Linaro/lava/blob/c38d449719d7e4dca3d07e6b5e9bb63d5a5579a9/lava_dispatcher/actions/deploy/removable.py#L151

Revert the previous changes to allow LAVA to detect that the deploy action
has finished.

This reverts commit 9dc1fafa.

Revert this changes since QA Report App tries to use this metadata and
currently rises the following exception:

    File "/app/testobjects.py", line 143, in lava_jobdata_extract_results
      t['group'] = testgroup['name']
    KeyError: 'name'

This causes tests results for v2023pre not being processed.

It is not clear if this metadata is used, however, currently it is not
possible to easily deploy a new version of QA Report app, so the best
approach is to revert this change.

Validating the job definitions when resubmitting them yields:

    Valid definition with warnings:
      extra keys not allowed
      @ data['actions[4]']['test']['definition']['name']

Get rid of those extra keys to make LAVA happier.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Validating the job definitions when resubmitting them yields:

    Valid definition with warnings:
      extra keys not allowed
      @ data['actions[2]']['deploy']['usb']['tool']

Get rid of the extra setting to make LAVA happier.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Commit cde077ec ("lava: amd64-upsquared6000: User a newer v2022 first
stage image") set the UP Squared 6000 1st stage image to a weekly build.
As the weekly image may get deleted sooner than later, let's use a
release point.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

When running the aum-rollback-blacklist test, u-boot must rollback to
the older version when the bootlimit of 3 has been reached.

Using just `boot` will bypass the boot count check, so we need to add
the check here in the device template, like it is done for the other
device types.

Fixes: infrastructure/apertis-issues#129
Fixes: infrastructure/apertis-issues#130

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>