1. 22 Dec, 2021 1 commit
  2. 26 Nov, 2021 1 commit
  3. 22 Nov, 2021 1 commit
  4. 06 Oct, 2021 1 commit
  5. 17 Aug, 2021 1 commit
  6. 07 Aug, 2021 3 commits
  7. 20 Jul, 2021 1 commit
  8. 27 Feb, 2021 3 commits
  9. 22 Feb, 2021 2 commits
    • Denis Pynkin's avatar
      Fix false positive tests results · 140debb5
      Denis Pynkin authored
      
      
      If we expect the failure of `apply_update_sync` we should treat
      only "1" return status as expected value.
      Return status "99" is reserved on unexpected failure of AUM itself and
      must indicate the failing test.
      This helps to avoid masking of AUM internal problems.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
      140debb5
    • Denis Pynkin's avatar
      lib: detect AUM crash · 5676d033
      Denis Pynkin authored
      
      
      If AUM is crashed by any reason (SIGSEGV for example) the function
      `apply_update_sync` don't detect that behavior and exit with error code
      after timeout (~8 min). This is leading to false positive result if we
      are expecting the update failure.
      
      Added the check of AUM restart by systemd and return code `99` for that case.
      Different error code allow to determine if the upgrade is failed as
      expected or we have bug in AUM code. Reduces the test time in case of
      AUM crash.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
      5676d033
  10. 23 Dec, 2020 3 commits
  11. 21 Dec, 2020 1 commit
  12. 20 Dec, 2020 1 commit
    • Denis Pynkin's avatar
      fix: correct check of the updated state · b5f1aaa6
      Denis Pynkin authored
      Commit 8f826964 contain the fix of ostree commit ID parsing.
      Before that commit the ID contained additional suffix (".0") and
      thus the comparison with `COMMIT_AFTER` always shows a difference
      and the test result was __always__ false positive: "pass".
      
      After applying the 8f826964
      
       commit we shed light to other issue --
      we saved a wrong ostree commit ID for later usage.
      In case if we prepare the "outdated" commit -- we must use it's ID
      as "starting" for the test.
      
      Moved the preparation of "outdated" ostree commit into the common
      function `prepare_outdated_commit()` and store the proper ostree
      commit ID as starting point.
      
      Additional side-effect fixed for OTA upgrades -- before current fix
      OTA tests were unstable, sometimes allowing to pass the check even
      with wrong ID written as starting point.
      This is caused by long queues in LAVA nowadays -- the build system may
      prepare and submit the new version while the test is waiting in queue.
      In that case the system do the real upgrade to the OS version newer
      than we have during the test submit.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
      b5f1aaa6
  13. 19 Dec, 2020 1 commit
  14. 17 Dec, 2020 3 commits
  15. 16 Dec, 2020 1 commit
    • Denis Pynkin's avatar
      Fix the commit ID parsing · 8f826964
      Denis Pynkin authored
      
      
      There were an arror in commit ID parsing from the output of:
        $ ostree admin status
        * apertis 334f57354221f0800b008d043c5c50683e83e8b6afa5880e95449a980132fa83.0
            origin refspec: origin:apertis/v2021pre/armhf-uboot/minimal
          apertis bab35cb1fe04e2fc11c3b462ebac0e38640173ebcff55ca326f838296a0121f5.0 (rollback)
            origin refspec: origin:apertis/v2020/armhf-uboot/minimal
      
      Some test contains incorrect boot ID detection, including the suffix
      `.0` which is an error. Hence fixing the issue in the initial script and
      all copy-paste copies.
      Signed-off-by: Denis Pynkin's avatarDenis Pynkin <denis.pynkin@collabora.com>
      8f826964
  16. 29 Jul, 2020 1 commit
  17. 26 Jul, 2020 1 commit
  18. 16 Jul, 2020 1 commit
    • Frederic Danis's avatar
      lib: Fix OTA update test failures · ecc1e308
      Frederic Danis authored
      
      
      aum-ota-signed test fails with the following traces:
      + testname=test-sign-no_signature
      + apply_update_sync -o
      + local RESULT=1
      + date +%Y-%m-%d %H:%M:%S
      + local BEFORE_UP_DATE=2020-07-14 08:02:30
      …
      Jul 14 08:02:40 apertis apertis-update-[667]: Ostree upgrade failed: Can't verify commit: signature: ed25519: no keys loaded: signed with unknown key
      + journalctl --since 2020-07-14 08:02:30 --unit apertis-update-manager
      + grep -qE Ostree already up to date
      + journalctl --since 2020-07-14 08:02:30 --unit apertis-update-manager
      + grep -qE Ostree upgrade failed
      + echo update failed
      update failed
      …
      + echo test-sign-no_signature: pass
      test-sign-no_signature: pass
      + testname=test-sign-update
      + mkdir -p /etc/ostree/trusted.ed25519.d
      + cp -av apertis.ed25519 /etc/ostree/trusted.ed25519.d/
      `apertis.ed25519' -> `/etc/ostree/trusted.ed25519.d/apertis.ed25519'
      + apply_update_sync -o
      + local RESULT=1
      + date +%Y-%m-%d %H:%M:%S
      + local BEFORE_UP_DATE=2020-07-14 08:02:40
      + + grep -qE Ostree already up to datejournalctl
       --since 2020-07-14 08:02:40 --unit apertis-update-manager
      + + journalctl --since 2020-07-14 08:02:40 --unit apertis-update-manager
      grep -qE Ostree upgrade failed
      + echo update failed
      update failed
      + RESULT=1
      + break
      + kill 707
      + kill 701
      + return 1
      + error_occured
      + set +x
      Job for generated-test-case-offline-upgrade.service failed because the control process exited with error code.
      See \"systemctl status generated-test-case-offline-upgrade.service\" and \"journalctl -xe\" for details.
      Command exited with non-zero status 1
      real	0m 16.77s
      user	0m 0.03s
      sys	0m 0.02s
      <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=offline-upgrade RESULT=fail>
      
      When apply_update_sync is called multiple time too quickly it can see
      messages from previous call and base its result on them.
      Signed-off-by: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
      ecc1e308
  19. 18 Jun, 2020 1 commit
  20. 30 Apr, 2020 1 commit
  21. 29 Apr, 2020 1 commit
  22. 28 Apr, 2020 1 commit
  23. 22 Apr, 2020 6 commits
  24. 20 Apr, 2020 3 commits