1. 07 Jun, 2021 1 commit
  2. 05 Jun, 2021 1 commit
  3. 28 May, 2021 2 commits
  4. 21 May, 2021 1 commit
  5. 10 May, 2021 2 commits
  6. 06 May, 2021 9 commits
  7. 05 May, 2021 1 commit
  8. 08 Mar, 2021 1 commit
    • Emanuele Aina's avatar
      lava: Fix common tests running out of storage on sdk · e9923f5f
      Emanuele Aina authored
      The common tests group currently blows up on LAVA when submitted to
      QEMU-based DUTs as we do for the SDK and base SDK images because the
      dispatcher runs out of disk space while unpacking the overlay before
      uploading it to the DUT:
          Job error: tar_in: tar subcommand failed on directory: /:
          tar: 0/tests/1_disk-rootfs-fsck/apertis-tests/.git/objects/pack/pack-c1d7de14a133c29fdcacfeef5eba98291ada6c91.pack:
          Wrote only 2048 of 10240 bytes tar: 0/tests/1_disk-rootfs-fsck/apertis-tests/.git/packed-refs:
          Cannot write: No space left on device
      In particular this is because the git repositoriee installed by the
      apparmor-gstreamer1.0 and gstreamer1.0-decode testcases used to ship a
      large copy of the Big Buck Bunny movie. Even if the test file has been
      dropped from the HEAD of both repositories in favor of the media sample
      file for the same movie pre-installed on the images, LAVA fails because
      it does not do a shallow checkout but it ends up putting the whole git
      hisotry in the overlay.
      To side-step the issue, move all the apparmor tests still in the
      `common-standalone` group to the `apparmor-standalone` group, but keep
      skipping them on minimal images.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
  9. 05 Mar, 2021 1 commit
  10. 01 Mar, 2021 1 commit
    • Denis Pynkin's avatar
      Revert "lava: Make the AUM tests logs work again the web UI" · 6bcb2584
      Denis Pynkin authored
      This reverts commit 0dc36df3
      Revert this commit since it is breaking tests submission to LAVA with
      `lqa` tool started in Apertis environment:
       Submitting job aum-ota-rollback-blacklist.yaml: <Fault 400: 'Problem
       with submitted job data: Loading job submission failed: while parsing
       a block mapping\n  in "<unicode string>", line 2, column 1\ndid not
       find expected key\n  in "<unicode string>", line 154, column 1.'>
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
  11. 24 Feb, 2021 2 commits
    • Emanuele Aina's avatar
      lava: Make the AUM tests logs work again the web UI · 0dc36df3
      Emanuele Aina authored
      Commit 39e6ec4f made `tar` output the extracted filenames while
      deployng the overlays and later commit 39e6ec4f made it
      customizable since the AUM tests do many reboot cycles each with their
      own (redundant) overlay deployment, causing the logs to grow massively
      and going over the limits imposed by the LAVA web UI, which refuses to
      display them and only offers to download them in JSON format.
      Unfortunately the fix on 39e6ec4f
       worked only partially and the
      overlays in the loop were still upacked in verbose mode, resulting in
      unreadable logs.
      For some reason that currently escapes me related to the way Jinja2
      imports work, re-importing the template with the macros from the
      looping template fixes the issue.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
    • Emanuele Aina's avatar
      gitlab-ci: Do not actually submit jobs to LAVA · 14f3a010
      Emanuele Aina authored
      Submitting tests to LAVA from this repository has been broken for a long
      time and has proven to be not useful. Yet, it generates plenty of noise
      on the LAVA side, so disable the actual submission.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
  12. 15 Feb, 2021 1 commit
  13. 04 Feb, 2021 2 commits
  14. 20 Jan, 2021 3 commits
    • Denis Pynkin's avatar
      lava: add flexible options for unpack with tar · 39e6ec4f
      Denis Pynkin authored
      For AUM tests unpack of overlay with tests in verbose mode
      produce too lot of almost useless information. This is the reason
      why the job log exceeding 5MB limit and should be downloaded as
      plain text which is hard to analyze.
      Added common macros `tar_unpack_cmd()` which create dynamic unpack
      string depending on variable `tar_additional_options` ('-v' by default).
      Additional verbose option for `tar` was switched off for all AUM tests
      to simplify log analysis in WEb interface.
      It is possible to override default options with `lqa` command, for
      example: `lqa -t tar_additional_options:""`.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
    • Denis Pynkin's avatar
      lava: fix variables quoting for AUM tests · f43a3a0b
      Denis Pynkin authored
      Without quoting they could be assumed as number which will lead to
      incorrect usage. For instance build `20210119.0130` was cut to
      `20210119.013` leading to incorrect path to delta URL construction.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
    • Frederic Danis's avatar
      psdk: Update SDK persistent test · 718fcc25
      Frederic Danis authored
      The new `psdk-test` perform the 3 previous tests (etc, home-user and
      sysroot) without user interaction.
      It can use a pre-downloaded virtual disk image, or directly the URL.
      Signed-off-by: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
  15. 19 Jan, 2021 1 commit
  16. 25 Dec, 2020 1 commit
    • Denis Pynkin's avatar
      lava/renesas: use the U-Boot for fdtfile setup · 22c0c4c4
      Denis Pynkin authored
      Starting from kernel 5.5 FDT names were split and
      renamed to align with config options. This leads to
      boot failure of old or new Apertis images depending of
      naming schema used in `fdtfile` environment variable.
      U-Boot used in Apertis and LAVA have additional feature
      allowing to try the legacy FDT naming schema in cases
      of boot failure with default naming schema.
      On v2021 for the switching branches test we have to boot
      images with old naming for DTB file in v2020 (5.4 kernel) and
      new naming schema in v2021 (5.9 kernel).
      So it is not possible to hardcode proper variable `fdtfile`
      for booting both versions in LAVA.
      Instead we remove hardcoded DTB file and use additional boot
      target `legacy_mmc0` which automatically set the "old" name
      for the DTB file in case if boot with a new one was failed.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
  17. 23 Dec, 2020 1 commit
    • Denis Pynkin's avatar
      ostree: remove redundant AUM testcases · c1230acf
      Denis Pynkin authored
      The most of the tests are covered by automatic tests or by
      other manual tests. Hence remove unneeded manual tests.
      Lower priority for manual OTA rollback test since we have an
      automation counterpair.
      We keep both rollback tests for offline and online upgrades to
      have a check point of our automation -- due complexity of the
      testing process, automatic test _may_ have errors or false-positive
      behavior in case if we change the AUM, U-Boot or libostree.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
  18. 22 Dec, 2020 3 commits
  19. 18 Dec, 2020 6 commits