Since these components are under development enable task-per-release to create different tasks depending on the branch where the test fails.

Signed-off-by: Sagar <SagarKishore.Benani@in.bosch.com>

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>

In commit 4d5bb092 some tweaks to LAVA callbacks were done, however,
additional tweaks are needed to allow LAVA to send test results
to qa.apertis.org.

Tweak the additional configurations to allow reports to appear in the
QA interface.

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

Vignesh Raman authored 2 years ago and Walter Lozano committed 2 years ago

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: Vignesh Raman <vignesh.raman@collabora.com>

Detlev Casanova authored 2 years ago and Walter Lozano committed 2 years ago

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.

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

Walter Lozano authored 2 years ago and Ariel D'Alessandro committed 2 years ago

AUM tests for amd64 were never fully enabled due to the lack of hardware
in LAVA. After adding support to the new UP Squared 6000 boards this has
changed, so re enable test on amd64 to make testing consistent across all
the supported boards.

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

Commit 2789c28c ("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>

Commit fddc555c ("lava: amd64-upsquared6000: Use v2022 1st stage image
with firmware pkgs") set the UP Squared 6000 1st stage image to a daily
build as it included the required firmware pkgs. As the daily image will
get deleted soon, let's use a weekly one until the next v2022 release it
out.

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

Ariel D'Alessandro authored 2 years ago and Walter Lozano committed 2 years ago

RPi AUM tests were disabled on Lava due to an issue on RPi4 U-boot.

The origin of this issue was that the same U-boot's defconfig
`rpi_arm64_defconfig` is used for both RPi3 and RPi4. This defconfig
sets the bootcount mmc dev/part to `0:1`. For RPi3 this works fine, as
mmc0 is the SD card, but on RPi4 mmc0 is used to control the SDIO for
wireless.

This has been fixed already by setting the aliases on RPi4 dtb for its
mmc devices. Thus, AUM tests can be re-enabled on RPi.

This reverts commit  4d06a3d1:

  Author: Frédéric Danis <frederic.danis@collabora.com>
  Date:   Wed Feb 16 17:07:05 2022 +0100

      lava: Prevent AUM tests to be generated for RPi board

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

The latest Apertis NFS images now include firmware pkgs required to
enable audio and the Intel AX210 wifi module on the UP Squared 6000
board.

Without these firmware pkgs, drivers will retry several times. Thus,
lots of kernel msgs are printed to the serial console, which makes LAVA
test fail to parse the login prompt.

Since we are currently in the release period and this is adding a lot
noise to the results, let's use the latest daily image. But note that
this should be updated quickly to a weekly release, before it becomes
unavailable.

Fixes: infrastructure/apertis-issues#171



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

Many comments in the test cases mention the Minnowboard as the target
reference board. This is now retired and replaced by the UP Squared 6000
board, so replace any occurrence.

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

The lava test templates have some comments on the timeouts referring to
the Minnowboard, now retired. Let's remove this old comments, but keep
the used timeouts, as that's the current setup working on LAVA.

A follow up task should revisit these timeouts and set them more tightly
if needed.

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

The Apertis v2022 image used to flash the testing images is reporting an
issue related to the wifi driver:

See https://lava.collabora.dev/scheduler/job/7001988#L1209
```
[   27.837322] iwlwifi 0000:02:00.0: minimum version required: iwlwifi-ty-a0-gf-a0-39
[   27.837324] iwlwifi 0000:02:00.0: maximum version supported: iwlwifi-ty-a0-gf-a0-66
[   27.837325] iwlwifi 0000:02:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git


[   27.847366] stack segment: 0000 [#1] SMP NOPTI
[   27.952703] CPU: 3 PID: 85 Comm: kworker/3:1 Tainted: G            E     5.15.0-trunk-amd64 #1  Debian 5.15.22-0~apertis1
[   27.964951] Hardware name: AAEON UPN-EHL01/UPN-EHL01, BIOS UNEHAM19 04/07/2022
[   27.973021] Workqueue: events request_firmware_work_func
[   27.978961] RIP: 0010:kfree+0x64/0x250
[   27.983150] Code: 80 48 01 dd 0f 82 f5 01 00 00 48 c7 c0 00 00 00 80 48 2b 05 fe 68 f0 00 48 01 c5 48 c1 ed 0c 48 c1 e5 06 48 03 2d dc 68 f0 00 <48> 8b 45 08 48 8d 50 ff a8 01 48 0f 45 ea 48 8b 55 08 48 8d 42 ff
[   28.004139] RSP: 0018:ffffb8e48023fcc0 EFLAGS: 00010207
[   28.009974] RAX: 00006f5940000000 RBX: 36415f5f0004000f RCX: 00000000000006bc
[   28.017946] RDX: 0000000000000000 RSI: ffffffffc0e16e86 RDI: 36415f5f0004000f
[   28.025916] RBP: 00d8e24923001000 R08: ffffffff9fa41940 R09: ffffb8e48023fbd8
[   28.033888] R10: ffff90a742874000 R11: 0000000000000000 R12: ffff90a7425572b8
[   28.041861] R13: ffff90a8a41b5900 R14: 0000000000000000 R15: ffff90a742557000
[   28.049834] FS:  0000000000000000(0000) GS:ffff90a8a4180000(0000) knlGS:0000000000000000
[   28.058874] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   28.065294] CR2: 0000565365b792b0 CR3: 00000001075a6000 CR4: 0000000000350ee0
[   28.073266] Call Trace:
[   28.075997]  <TASK>
[   28.078341]  iwl_dealloc_ucode+0x36/0x110 [iwlwifi]
[   28.083809]  iwl_req_fw_callback+0x2cf/0x23d0 [iwlwifi]
[   28.089650]  ? free_fw_priv+0x9f/0x110
[   28.093835]  ? _request_firmware+0x42f/0x640
[   28.098604]  ? kfree+0x1f8/0x250
[   28.102206]  ? _request_firmware+0x42f/0x640
[   28.106974]  request_firmware_work_func+0x4a/0x90
[   28.112229]  process_one_work+0x1ee/0x390
[   28.116707]  worker_thread+0x53/0x3e0
[   28.120793]  ? process_one_work+0x390/0x390
[   28.125454]  kthread+0x124/0x150
[   28.129059]  ? set_kthread_struct+0x40/0x40
[   28.133731]  ret_from_fork+0x1f/0x30
[   28.137727]  </TASK>
[   28.140163] Modules linked in: sha512_generic(E) snd_intel_sdw_acpi(E) snd_hda_codec(E) ctr(E) snd_hda_core(E) drbg(E+) aesni_intel(E+) snd_hwdep(E) asus_nb_wmi(E) iwlwifi(E) asus_wmi(E) crypto_simd(E) snd_pcm(E) ansi_cprng(E) cryptd(E) iTCO_wdt(E) platform_profile(E) mmc_block(E) intel_cstate(E) mei_hdcp(E) evdev(E) snd_timer(E) intel_pmc_bxt(E) battery(E) cfg80211(E) snd(E) ecdh_generic(E+) sparse_keymap(E) iTCO_vendor_support(E) intel_wmi_thunderbolt(E) wmi_bmof(E) soundcore(E) efi_pstore(E) pcspkr(E) rfkill(E) watchdog(E) ecc(E) ti_adc128s052(E) crc16(E) industrialio(E) i915(E) ttm(E) drm_kms_helper(E) sdhci_pci(E) cec(E) cqhci(E) ahci(E) rc_core(E) libahci(E) sdhci(E) drm(E) libata(E) mei_me(E) mmc_core(E) scsi_mod(E) mei(E) scsi_common(E) intel_pmc_core(E) acpi_tad(E) acpi_pad(E) button(E) fuse(E) configfs(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) nfsv3(E) nfs_acl(E) nfs(E) lockd(E) grace(E) sunrpc(E) fscache(E) netfs(E) spi_pxa2xx_platform(E) dw_dmac(E) dw_dmac_core(E)
[   28.140232]  crc32_pclmul(E) crc32c_intel(E) igb(E) i2c_i801(E) i2c_smbus(E) i2c_algo_bit(E) dca(E) igc(E) xhci_pci(E) ptp(E) xhci_hcd(E) pps_core(E) usbcore(E) intel_lpss_pci(E) intel_lpss(E) usb_common(E) idma64(E) fan(E) wmi(E) video(E) pinctrl_elkhartlake(E)
[   28.263736] ---[ end trace 2553bae38d1333f9 ]---
```

To overcome this, use the following image as it includes a newer kernel
v5.15.34, where the iwlwifi issue is fixed: weekly/v2022/20220803.0154

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

Use a more recent image, as there is no support for the UP Squared 6000
board in v2019.1.

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

The recently added UP Squared 6000 device uses the eMMC for deployment,
which is different from the default setting (sd-card). Let's add a
parameter so each LAVA device can set the deploy device in each case.

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

The Apertis amd64 reference platform -MinnowBoard Turbot board- went out
of production a while ago and are no longer available. The UP Squared
6000 board has been chosen as the new reference platform, so let's
replace it.

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

Now that QA Report App renders the test cases in its interface the deploy
using apertis-test-cases-web is not longer needed.

Drop the deploy of this repo and also the deploy in forks to avoid confusions.

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

The goal of this test is to ensure we can execute the getting-started
instructions in the apertis-image-recipes README from inside the Apertis
SDK running on Virtualbox.

We don't actually have Virtualbox in LAVA, so it must be simulated.
As Virtualbox doesn't support nested KVM virtualization, let's remove
the KVM module. This should trigger the chroot-based Debos backend
instead of the fakemachine one"

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

This test was created to verify some DBUS robustness patches that ended
up not being accepted upstream.

The downstream patches have been dropped since v2019 when we rebased to
Debian, so this test doesn't have value anymore.

Avoid random failures by removing it.

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

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

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

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

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

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

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

LAVA version 2021.11 introduces a change in the way paths in compressed
overlays are handled breaking Apertis tests.

Fix the issue by specifying the path to be use to extract the compressed
overlay.

Additional information:

https://gitlab.collabora.com/lava/lava/-/commit/07048f042c65202eb75ac874cc93eabd2d96cd54



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

aum-offline-upgrade-branch is not generated with following error:
template variable not defined in aum-offline-upgrade-branch: 'osname' is undefined

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

RPi fails on AUM tests on Lava due to U-Boot.
This introduce a workaround to prevent those tests to be run.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

arm64-rpi64 bundles don't exist.
RPi64 boards use arm64-uboot bundles for the upgrade.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

This reverts commit c000fc66.

This simplification breaks the qa-report-app and would make to much
confusion in that code. Let's keep nfsroot

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

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

This is to be closer to the type that is used in apertis-lava-recipes.
This way, we avoid using more variables to cover image type (nfs) and
test type (nfsroot). Now, they are both called nfs.

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

This is the type used by the nfs images generated on the
apertis-lava-recipes repository.

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

This program is used to send the generated lava jobs to a lava server
using lqa.

It also sends the given metadata to the lavaphab bridge.

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

This program does not use LQA to generate the job descriptions.

It is capable of finding all the tests for a given image and group them
into the adequate template.

Each job is written into a yaml file: job-${image_name}-${group}.yaml

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

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

These tests were not referenced by any template and therefore don't have
a group.

Because no templates were referencing them, they were not executed as
part of the automated test suite. Their removal doesn't affect the test
results.

This test is run as part of the sanity checks.

Setting the type to sanity allows the generate-jobs script to know that
this test is not supposed to be in any group and can be ignored when
generating job files.

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