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

add step to install `xserver-xephyr` pkg explicitly

Signed-off-by: SivaKrishnaPrasad <sivakrishnaprasad.chinthalapudi@in.bosch.com>

Following the same approach used at image generation, disable HTTP 2 in
flatpak to overcome connections issues as OSTree does not support retries.

infrastructure/apertis-image-recipes!612
https://github.com/ostreedev/ostree/issues/2570
infrastructure/apertis-issues#436



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

With apertis-dev-tools 0.2023.4, a new mandatory flag was added
for sdk-import-debian-package. This new flag allows to pass the reason
for importing the package. See commit 1588bc10 in `pkg/apertis-dev-tools`

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

`aa-status` was merged back in `apparmor` in 3d5b5245
during the bookworm rebase because the reason of the split was no
longer valid.

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

Walter Lozano authored 1 year ago and Ryan Gonzalez committed 1 year ago

After relaxing hmi-switch-graphical-applications to use any application
some instructions were not properly updated. Update the test case to
be coherent with the new approach.

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

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>

telepathy is no longer used for testing and not available in
Apertis since the Bookworm rebase.

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

The test hmi-switch-graphical-applications requests to open Fonts application
which is installed by default in HMI images via Flatpak, but not installed
on SDK. Since the test can be run with any graphical application, relax
it and mention Fonts only as a suggestion.

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

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

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

This test is expected to be run on a system with its rootfs on an eMMC storage
and not on a USB device. Using a rootfs from a USB device can lead to
failures like the systemd service 'usbmount@dev-sda1.service' failing to
start since /dev/sda1 is already mounted at /boot/efi.

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

The sanity manual test is the first test run to confirm the health of the
image. For this reason, the test itself states that no other manual test
should run if there is a failure.

This policy aims to avoid running tests on an image which is not healthy
enough since the results will not be valid. This policy is too strict,
since due to failure in one are, like WiFi, will block the rest of the
tests.

To provide a better trade off, update the policy to avoid running other
manual tests until the issue is triaged.

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

Walter Lozano authored 1 year ago and Andre Moreira Magalhaes committed 1 year ago

Improve the wording of the pre conditions section in the secure boot test
to instruct the flashing to the correct u-boot image based on the release
under test.

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

Signed-off-by: SivaKrishnaPrasad <sivakrishnaprasad.chinthalapudi@in.bosch.com>

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>

Siva Krishna Prasad Chinthalapudi authored 2 years ago and Dylan Aïssi committed 1 year ago

Signed-off-by: SivaKrishnaPrasad <sivakrishnaprasad.chinthalapudi@in.bosch.com>

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

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

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

In commit 5bf3c4a9 tests for amd64 board were re enabled after adding
support for Up Squared 6000 board, and having enough boards in LAVA.

After this, it was seen that tests that relies in bootcount fail and
require a rework to align u-boot and uefi.

In the mean time, to avoid creating noise and masking issues disable
tests that rely in bootcount.

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

The use of the git repos pointing at v2023dev1 was introduced in 6ae11598
which was merged later on v2023dev2, causing the branching script not
being able to update the branch name.

Manually fix the issue.

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

In some use cases it is useful to only run some test cases, with that in
mind add the support to them when generating the jobs.

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>

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

The previous code would only ever check if the architecture was directly
listed in the test case, which meant it excluded the visibility
suffixes.

https://phabricator.apertis.org/T8949

This was getting rendered as a messy plain-text paragraph.

https://phabricator.apertis.org/T8949

Because the test logs are private, the visibility is '-internal', so
update the test cases to match.

https://phabricator.apertis.org/T8949



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

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.