Skip to content
Snippets Groups Projects
  1. Dec 23, 2020
    • Denis Pynkin's avatar
      ostree: remove redundant AUM testcases · e71c0619
      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: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      e71c0619
    • Denis Pynkin's avatar
      fix: correct name for aum-offline-upgrade-branch · 523d0ac9
      Denis Pynkin authored
      
      Fixed the name for the test -- it was the same as already existing.
      
      Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      523d0ac9
    • Denis Pynkin's avatar
      lava: fix the boot of U-Boot for rollback · 9501ae27
      Denis Pynkin authored
      
      The correct testing of rollback relies to U-Boot behavior.
      In Apertis we expect the U-Boot should to use rollback configuration
      in case if boot counter is above the limit.
      
      Unfortunately we break the normal boot of SabreLite and Renesas boards
      in LAVA by running direct boot with `run bootcmd_mmc0` command.
      
      This completely breaks the correct workflow for rollback since it relies
      to command `altbootcmd` which is a part of Apertis distro boot
      modification.
      The U-Boot bootloader should to drop the warning if boot counter is
      truggering the rollback:
      
        File System is consistent
        file found, deleting
        File System is consistent
        Warning: Bootlimit (3) exceeded. Using altbootcmd.
      
      and proceed with the call of `altbootcmd` instead of `distro_bootcmd`.
      But since we stop the boot and do a manual boot from mmc0, alternative
      boot is never called.
      
      To proceed with the correct behavior after breaking the boot process we
      check the boot limit additionally and choose the proper boot variant.
      
      Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      9501ae27
    • Denis Pynkin's avatar
      fix: path to repo "apertis-tests" · 190134e9
      Denis Pynkin authored
      The path to git repository should be:
       https://gitlab.apertis.org/pkg/apertis-tests
      
      otherwise LAVA throw an error:
       Infrastructure error: Unable to fetch git repository
       'https://gitlab.apertis.org/infrastructure/apertis-tests
      
      '
      
      Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      190134e9
  2. Dec 18, 2020
  3. Nov 26, 2020
  4. Nov 25, 2020
  5. Nov 20, 2020
  6. Nov 02, 2020
  7. Sep 30, 2020
  8. Sep 21, 2020
    • Emanuele Aina's avatar
      lava: Fix NFS tests on Renesas boards · db86f30d
      Emanuele Aina authored
      
      After commit 45dae71b fixed the boot on Renesas boards with
      linux >= 5.7 due to the change of the dtb name, the tests exercising
      the NFS boot of the current release as the first stage broke since
      they do not use `boot_commands` and thus didn't get the override.
      
      To fix that, rather than constructing the path to the DTB from the
      LAVA device name, which no longer match the board type with
      linux >= 5.7, explicitly pass the DTB path for the first stage and the
      release under test separately.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      db86f30d
  9. Sep 16, 2020
  10. Sep 07, 2020
  11. Aug 27, 2020
  12. Aug 26, 2020
  13. Aug 21, 2020
  14. Aug 20, 2020
  15. Aug 18, 2020
  16. Aug 14, 2020
  17. Jul 24, 2020
    • Denis Pynkin's avatar
      lava: fix Renesas M3 boot with kernel 5.7 · 45dae71b
      Denis Pynkin authored
      
      In commit 83772e1 and later commits DTB names in Linux kernel was
      renamed to align names with config options.
      Hence the old DTB name `r8a7796-m3ulcb.dtb` is `8a77960-ulcb.dtb` for
      Renesas M3 boards used in LAVA.
      
      Old U-Boot versions are using the old naming schema including version
      used in v2021dev3 atm.
      
      This commit set proper name only for v2021dev3 branch allowing to boot
      images for Renesas boards in LAVA.
      
      Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      45dae71b
  18. Jul 15, 2020
    • Martyn Welch's avatar
      Separate out test case generation from deployment · 8e0c0e45
      Martyn Welch authored and Emanuele Aina's avatar Emanuele Aina committed
      
      Rather than looping over branches (in included template from `pages`),
      generate the test cases here, provide these as an artifact and deploy
      in a separate job. This avoids the regeneration of pages that have
      not changed.
      
      Use the apertis-test-cases-web as part of a multi-project pipeline to
      deploy. Remove the deployment tools from this branch.
      
      Whilst we are here, utilise an environment variable for the release to
      make it easier to migrate this between releases.
      
      Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
      8e0c0e45
Loading