1. 21 Sep, 2021 1 commit
  2. 30 Aug, 2021 2 commits
  3. 23 Aug, 2021 1 commit
  4. 21 Aug, 2021 1 commit
  5. 16 Aug, 2021 4 commits
  6. 15 Aug, 2021 1 commit
  7. 09 Aug, 2021 1 commit
    • ci: remove the docker entrypoint · b140e22e
      Omitting an entrypoint.sh to configure the container and instead
      depending on docker primitives allows us to be more portable.  (If a
      distribution uses a different mechanism for adding users, we need not
      have multiple entrypoint.sh files or invariants within it; instead we
      can configure that in the dockerfile itself along with all the other
      distribution specific components.)
      Edward Thomson committed
  8. 04 May, 2021 1 commit
  9. 15 Jan, 2021 1 commit
  10. 22 Dec, 2020 1 commit
  11. 23 Nov, 2020 2 commits
  12. 18 Nov, 2020 1 commit
  13. 20 Jul, 2019 3 commits
    • azure: move build scripts into "azure-pipelines" directory · ffac520e
      Since we have migrated to Azure Pipelines, we have deprecated and
      subsequentally removed all infrastructure for AppVeyor and
      Travis. Thus it doesn't make a lot of sense to have the split
      between "ci/" and "azure-pipelines/" directories anymoer, as
      "azure-pipelines/" is essentially our only CI.
      
      Move all CI scripts into the "azure-pipelines/" directory to have
      everything centrally located and to remove clutter in the
      top-level directory.
      Patrick Steinhardt committed
    • tests: execute leak checker via CTest directly · d827b11b
      Right now, we have an awful hack in our test CI setup that extracts the
      test command from CTest's output and then prepends the leak checker.
      This is dependent on non-machine-parseable output from CMake and also
      breaks on various ocassions, like for example when we have spaces in the
      current path or when the path contains backslashes. Both conditions may
      easily be triggered on Win32 systems, and in fact they do break our
      Azure Pipelines builds.
      
      Remove the awful hack in favour of a new CMake build option
      "USE_LEAK_CHECKER". If specifying e.g. "-DUSE_LEAK_CHECKER=valgrind",
      then we will set up all tests to be run under valgrind. Like this, we
      can again simply execute ctest without needing to rely on evil sourcery.
      Patrick Steinhardt committed
    • fuzzers: provide test targets · 86ecd600
      Instead of having to find the fuzzer executables in our Azure test
      scripts, provide test targets for each of our fuzzers that will
      run them with the correct paths.
      Patrick Steinhardt committed
  14. 05 Jul, 2019 1 commit
  15. 25 Jun, 2019 1 commit
  16. 24 Jun, 2019 2 commits
  17. 10 Jun, 2019 3 commits
  18. 13 Feb, 2019 1 commit
  19. 28 Jan, 2019 1 commit
  20. 20 Jan, 2019 1 commit
  21. 19 Jan, 2019 3 commits
  22. 11 Jan, 2019 1 commit
  23. 28 Nov, 2018 1 commit
  24. 30 Oct, 2018 2 commits
  25. 26 Oct, 2018 2 commits
  26. 25 Oct, 2018 1 commit