1. 22 Feb, 2019 1 commit
  2. 13 Feb, 2019 1 commit
  3. 23 Sep, 2018 1 commit
    • Antonio Terceiro's avatar
      lxc/create-testbed: avoid cleaning up valid containers · 2bee4565
      Antonio Terceiro authored
      Sometimes, the creation of a new testbed fails for various reasons (some
      essential package) breaks debootstrap, or something fails to download.
      Those failures are already handled by autopkgtest-build-lxc: the old
      container is only replaced by the new one in case of success.  In that
      case, it's OK for debci to just keep using the older container since it
      will be upgraded before running any tests anyway.
      
      The only case where we indeed want to remove containers is when the
      customizations needed by debci are not successfully applied.
      2bee4565
  4. 09 Sep, 2018 1 commit
  5. 04 Aug, 2018 4 commits
  6. 02 Aug, 2018 1 commit
  7. 26 May, 2018 1 commit
  8. 09 May, 2018 1 commit
  9. 16 Mar, 2018 1 commit
  10. 08 Mar, 2018 1 commit
  11. 07 Mar, 2018 1 commit
  12. 28 Feb, 2018 1 commit
  13. 26 Feb, 2018 2 commits
  14. 27 Jan, 2018 2 commits
  15. 22 Nov, 2017 3 commits
    • Antonio Terceiro's avatar
      Add support for migration tests · fd88a74d
      Antonio Terceiro authored
      A migration is a test run test where you want to check if package X can
      be migrated from suite A (e.g. Debian unstable) to suite B (e.g. Debian
      testing). In this case, you run the tests on a base test bed from suite
      B, but add APT sources for suite A and pin the packages you want to
      migrate to be obtained from there. This can be used to test either new
      versions of package X itself, or packages that depend on it.
      
      Beying unstable → testing migration, this can also be used to test
      security updates, backports, etc.
      
      debci-test, and debci-enqueue can now take two extra options:
      
      --trigger: specifies the reason why this test is being performed. For
      debci, this is just a string and has no special meaning. This string is
      stored together with the test artifacts, and will also eventually be
      displayed in JSON data, and in the UI.
      
      --pin-packages=RELEASE=pkg,src:pkg. Adds APT sources for RELEASE, and
      pins the specified packages to be obtained from RELEASE. `src:pkg`
      expand to all binary packages from source package `pkg`. This requires
      autopkgtest >= 5.1.
      fd88a74d
    • Antonio Terceiro's avatar
      backends/fake: improve logging · 2296f395
      Antonio Terceiro authored
      2296f395
    • Antonio Terceiro's avatar
      Extract autopkgtest calls into a central helper program · 9c62e036
      Antonio Terceiro authored
      This will be used to centralize extra options that we want to pass to
      autopkgtest that are backend-independent.
      9c62e036
  16. 12 Oct, 2017 1 commit
  17. 26 Jul, 2017 1 commit
  18. 23 Jul, 2017 1 commit
  19. 22 Jul, 2017 2 commits
  20. 02 Jul, 2017 1 commit
  21. 25 Oct, 2016 1 commit
  22. 25 Aug, 2016 1 commit
  23. 02 Aug, 2016 1 commit
  24. 29 Jul, 2016 1 commit
  25. 04 Jun, 2016 1 commit
  26. 17 Apr, 2016 1 commit
  27. 11 Apr, 2016 4 commits
  28. 27 Mar, 2016 1 commit
  29. 30 Nov, 2015 1 commit