- Nov 20, 2024
-
-
Walter Lozano authored
Fix typo in file name to allow a proper render of the website. Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
- Nov 07, 2024
-
-
Walter Lozano authored
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
- Oct 21, 2024
-
-
Currently there are several AUM tests that are being executed in LAVA that ensures that the different scenarios are covered. Unfortunately due to the nature of how LAVA works, these tests do not take into account an important piece of software, the bootloader u-boot. The bootloader is responsible of two important things to propoerly handle the rollback: - Increment the bootcount on each boot attempt - Switch to an alternative boot method in case of failure To ensure that the whole system is working add a new manual test case. Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
- Sep 24, 2024
-
-
Dylan Aïssi authored
Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Sep 18, 2024
-
-
Dylan Aïssi authored
Since Bookworm, policykit-1 is a transitional package and will be removed in Trixie. Required tools are now in polkitd. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Sep 16, 2024
-
-
Walter Lozano authored
In order to provide better explanation on how to configure input/output devices and flatpak operations, move the steps to the website. Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
- Sep 09, 2024
-
-
Walter Lozano authored
The U-boot version in LAVA for RPi4 has been updated to 2024.01+dfsg-1+apertis7bv2025dev3b1 which supports a new layout for RPi4 to allow larger kernels to be used. The previous U-boot version in LAVA for RPi4 was 2021.10+dfsg-1+apertis10bv2022.1b3 which had different default environment, witch supported distro_boot as command. By default Apertis relied in distro_boot which was the standard way of booting distributions in previous U-boot version. With the new version U-boot the boot command needs to be adapted to use bootflow https://docs.u-boot.org/en/stable/develop/bootstd.html Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
Walter Lozano authored
This reverts commit 85295ff2 as a first step to adapt to the new version of U-boot. Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
Dylan Aïssi authored
Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Sep 06, 2024
-
-
Walter Lozano authored
Now that RPi4 is enabled we can enable HMI tests. Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
- Sep 02, 2024
-
-
Dylan Aïssi authored
Both tests are testing the Flatpak Apps handling (install, run, uninstall and re-install), so let's merge them into a unique test case. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Aug 26, 2024
-
-
Dylan Aïssi authored
Actually, installing Flatpak Apps is not really part of the test, but more a pre-condition of the test. Moreover, the Apertis repository and org.apertis.hmi.totem are not installed by default on SDK images. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Aug 19, 2024
-
-
Walter Lozano authored
During the branching a set of changes were missing, so apply them to really bump to v2025pre. Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
- Aug 15, 2024
-
-
Apertis CI authored
Signed-off-by: Apertis CI <devel@lists.apertis.org>
-
- Jul 25, 2024
-
-
Walter Lozano authored
The u-boot configuration in LAVA makes kernel image overlap with DTBs preventing the board to boot. To workaround this issue, set the correct values in the template while waiting for a proper fix in LAVA. pkg/linux!339 Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
- Jul 08, 2024
-
-
Tests should be moved to test group in gitlab, in this process move sdk-debos-image-building tests. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jun 27, 2024
-
-
Dylan Aïssi authored
Tests should be moved to test group in gitlab, in this process move docker-test tests. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jun 26, 2024
-
-
Tests should be moved to test group in gitlab, in this process move flatpak-run-demo-cli-app tests. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jun 24, 2024
-
-
Dylan Aïssi authored
Tests should be moved to test group in gitlab, in this process move ade tests. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jun 06, 2024
-
-
Dylan Aïssi authored
Having many tests on the same group does make the LAVA overlay too big for devices with small amount of free space. Thus some tests randomly fail due to lack of space. To make things worse, some old tests rely in packages like python which are not part of the images and need to be installed, consuming extra space. To workaround this issue, split the test group in two, moving tests with similar dependencies to a new to reduce the amount of space required per group. This will be fixed once tests will be moved from pkg/apertis-tests to tests/ but in the meantime let's do the split to reduce the chance of random failures. Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jun 03, 2024
-
-
Walter Lozano authored
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>
-
- May 23, 2024
-
-
Apertis CI authored
Signed-off-by: Apertis CI <devel@lists.apertis.org>
-
- May 15, 2024
-
-
Martyn Welch authored
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>
-
- May 10, 2024
-
-
Martyn Welch authored
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>
-
- May 09, 2024
-
-
Signed-off-by: Akhilesh Dandavati <akhilesh.dandavati@in.bosch.com>
-
- May 07, 2024
-
-
Martyn Welch authored
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>
-
- Apr 22, 2024
-
-
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>
-
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>
-
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>
-
Since these tests also are applicable to AMD 64 let's run them. Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
-
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>
-
- Apr 15, 2024
-
-
Signed-off-by: Balasubramanian Raju <Raju.Balasubramanian@in.bosch.com>
-
Signed-off-by: Sudarshan C P <sudarshan.cp2@in.bosch.com>
-
Signed-off-by: Sudarshan C P <sudarshan.cp2@in.bosch.com>
-
- Mar 26, 2024
-
-
Walter Lozano authored
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>
-