Skip to content
Snippets Groups Projects
  1. Nov 14, 2022
  2. Nov 11, 2022
  3. Nov 10, 2022
  4. Oct 31, 2022
  5. Oct 24, 2022
  6. Oct 20, 2022
    • Walter Lozano's avatar
      Revert "lava: Drop a bunch of spurious `name:` keys" · 79a2b0df
      Walter Lozano authored
      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.
      79a2b0df
  7. Oct 19, 2022
    • Edmund Smith's avatar
      Restore the previous dry run behaviour · 03262fe5
      Edmund Smith authored and Andre Moreira Magalhaes's avatar Andre Moreira Magalhaes committed
      The way test submission works changed significantly when we switched
      to using the lava_runner. In that change set, I preserved the logic
      around when the submit tasks ran, such that they only ran when a valid
      LAVA configuration existed in the job variables, and when the pipeline
      is not for a merge request.
      
      In repository preceding those changes, there was a valid LAVA
      configuration, but the test submission was given `--dry-run` so that
      we would run our templating, but stop short of submitting the jobs,
      even though we required a valid LAVA configuration to exist.
      
      In the repository after these changes, there is not a valid LAVA
      configuration (since the required variables changed) and now the test
      generation step is no longer occurring on pipelines. Moreover, if we
      made the LAVA configuration valid for the state we have now, it would
      both generate and run the tests, because the generation and run steps
      have identical rules governing them in CI.
      
      Therefore, remove the checks for a valid LAVA configuration from the
      generation step. This means we do not need a valid LAVA configuration
      in order to get the same behaviour we had before: generate the tests,
      but do not submit them.
      03262fe5
  8. Oct 13, 2022
  9. Sep 26, 2022
  10. Sep 23, 2022
  11. Sep 16, 2022
  12. Sep 08, 2022
  13. Sep 01, 2022
  14. Aug 31, 2022
    • Edmund Smith's avatar
      Actually move file to reflect new naming · f4c00ce8
      Edmund Smith authored and Sjoerd Simons's avatar Sjoerd Simons committed
      f4c00ce8
    • Edmund Smith's avatar
      Rename stages to match new behaviour · 6461c6f3
      Edmund Smith authored and Sjoerd Simons's avatar Sjoerd Simons committed
      6461c6f3
    • Edmund Smith's avatar
      Use the new generate-test-pipeline tool · 76de4e09
      Edmund Smith authored and Sjoerd Simons's avatar Sjoerd Simons committed
      These changes are made to demonstrate to client repository owners how
      to use the new tool for best effect. The tests from this repository
      are not now run as standard, and the base configuration cannot be run
      because the Apertis build ids are unset. Leaving the tests in an
      obsolete state seems actively harmful; the alternative is simply to
      remove the testing infrastructure entirely, but that makes it more
      difficult to find a fully worked example of how all the tools this
      repo provides fit together.
      
      Up until now, the approach has been to run two commands back-to-back:
      first generate the tests (as YAML), then submit them to Lava with
      lava-submit.py. Using the new generate-test-pipeline.py tool, we
      generate a pipeline which will run all the generated test files. We
      can then define a new trigger job for every existing submit job to
      execute the generated pipeline.
      76de4e09
    • Edmund Smith's avatar
      Add a tool to generate test pipelines · 30c3e29e
      Edmund Smith authored and Sjoerd Simons's avatar Sjoerd Simons committed
      generate-test-pipeline.py can replace lava-submit.py. The latter will
      submit a batch of test files to Lava, and return the ids for further
      monitoring as required. This model, however, prevents the Lava jobs
      themselves from making use of short-lived tokens like CI_JOB_TOKEN,
      because the job tokens available at the point of submission will
      expire with the completion of the submit job.
      
      This new tool produces a Gitlab YAML pipeline file, suitable for use
      in a subsequent trigger job. Each test file will have its own Gitlab
      job in the pipeline, and that Gitlab job will run using the Lava
      runner, which means live logs will be available, and all tokens will
      remain valid for the duration of the job.
      
      Note that we are still generating this pipeline in a job that has
      already terminated before the Lava jobs begin, so we cannot use our
      own CI_JOB_TOKEN in the test files. However, we can use the new
      templating feature of the lava runner to request that the individual
      test job's own CI_JOB_TOKEN be substituted into the Lava job before
      it is submitted by the Lava runner.
      
      If you are generating jobs in the standard way, using generate-jobs.py,
      you need to escape the templating you want the Lava runner to perform,
      so URLs might look like:
      
         https://gitlab-ci-token:{{ '{{job.CI_JOB_TOKEN}}' }}@my.gitlab.example/my/repo.git
      
      After template substitution by generate-jobs.py, the Lava runner will
      now see a URL of the form
      
         https://gitlab-ci-token:{{job.CI_JOB_TOKEN}}@my.gitlab.example/my/repo.git
      
      and will substitute its own CI_JOB_TOKEN before submitting the
      job. This will work for any of a job's associated CI variables, as
      needed.
      30c3e29e
  15. Aug 29, 2022
  16. Aug 17, 2022
  17. Aug 09, 2022
    • Ariel D'Alessandro's avatar
      lava: amd64-upsquared6000: User a newer v2022 first stage image · fd349817
      Ariel D'Alessandro authored
      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: default avatarAriel D'Alessandro <ariel.dalessandro@collabora.com>
      fd349817
  18. Aug 02, 2022
  19. Jul 20, 2022
  20. Jun 29, 2022
    • Ariel D'Alessandro's avatar
      Revert "lava: Prevent AUM tests to be generated for RPi board" · 1f67f61c
      Ariel D'Alessandro authored and Walter Lozano's avatar Walter Lozano committed
      
      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: default avatarAriel D'Alessandro <ariel.dalessandro@collabora.com>
      1f67f61c
  21. Jun 22, 2022
  22. Jun 16, 2022
  23. Jun 07, 2022
  24. Jun 06, 2022
    • Ariel D'Alessandro's avatar
      sdk-debos-image-building: Remove kvm_intel module · 77342f3e
      Ariel D'Alessandro authored
      
      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: default avatarAriel D'Alessandro <ariel.dalessandro@collabora.com>
      77342f3e
  25. Jun 02, 2022
  26. May 27, 2022
  27. May 19, 2022
Loading