1. 18 Nov, 2020 1 commit
  2. 13 Mar, 2020 1 commit
  3. 07 Feb, 2020 2 commits
  4. 04 Feb, 2020 2 commits
  5. 24 Jan, 2020 3 commits
  6. 20 Jul, 2019 4 commits
    • azure-pipelines: make gitdaemon tests work on Win32 · 415ee616
      On Win32 builds, the PID file created by git-daemon contained in invalid
      PID that we were not able to kill afterwards. Somehow, it seems like the
      contained PID was wrapped in braces. Consequentially, kill(1) failed and
      thus caused the build to error.
      
      Fix this by directly grabbing the PID of the spawned git-daemon process.
      Patrick Steinhardt committed
    • 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
  7. 24 Jun, 2019 1 commit
  8. 10 Jun, 2019 1 commit
  9. 20 Jan, 2019 1 commit
  10. 19 Jan, 2019 1 commit
  11. 11 Jan, 2019 1 commit
  12. 28 Nov, 2018 1 commit
  13. 30 Oct, 2018 2 commits
  14. 26 Oct, 2018 1 commit
  15. 23 Oct, 2018 1 commit
  16. 21 Oct, 2018 1 commit
  17. 29 Sep, 2018 1 commit
  18. 11 Sep, 2018 1 commit
  19. 10 Sep, 2018 1 commit
    • ci: only run the exact named test · 7e353b7a
      Our CI test system invokes ctest with the name of the given tests it
      wishes to invoke.  ctest (with the `-R` flag) treats this name as a
      regular expression.  Provide anchors in the regular expression to avoid
      matching additional tests in this search.
      Edward Thomson committed
  20. 03 Aug, 2018 3 commits
  21. 26 Jul, 2018 6 commits