1. 30 Aug, 2023 2 commits
  2. 23 Aug, 2023 2 commits
  3. 13 May, 2023 2 commits
    • streams: sockets are non-blocking and can timeout · fad90428
      Make socket I/O non-blocking and add optional timeouts.
      
      Users may now set `GIT_OPT_SET_SERVER_CONNECT_TIMEOUT` to set a shorter
      connection timeout. (The connect timeout cannot be longer than the
      operating system default.) Users may also now configure the socket read
      and write timeouts with `GIT_OPT_SET_SERVER_TIMEOUT`.
      
      By default, connects still timeout based on the operating system
      defaults (typically 75 seconds) and socket read and writes block.
      
      Add a test against our custom testing git server that ensures that we
      can timeout reads against a slow server.
      Edward Thomson committed
    • ci: update to poxygit v0.6.0 · 933b04c2
      v0.6.0 of poxygit add support for throttling connections to test
      timeouts and low-bandwidth situations.
      Edward Thomson committed
  4. 12 Feb, 2023 1 commit
  5. 09 Feb, 2023 3 commits
    • ci: convert PATH correctly to Cygwin format on Windows · b857122f
      We provide `BUILD_PATH` to our build script; provide it and mutate
      `PATH` when running our tests as well.
      
      We were previously using `cygpath` to try to convert a _list_ of Windows
      paths into cygwin / Unix style `PATH` format. This does not work -- it
      treats the path list as a single path (with semicolons -- understandably
      as those are allowed characters in a Windows path).
      
      For example, `C:\One;C:\Two;C:\Three` is converted to
      `/c/one;c:/two;c:/three`.
      
      Add a new function to convert path lists, so that paths are split by
      semicolon and fed to `cygpath` independently, then re-joined with a
      colon. This means that our example `C:\One;C:\Two;C:\Three` is correctly
      converted to `/c/one:/c/two:/c/three`.
      Edward Thomson committed
    • ci: limit test runner to build path · a7bc32ed
      We provide `BUILD_PATH` to our build script; provide it and mutate
      `PATH` when running our tests as well.
      Edward Thomson committed
    • ci: isolate the home directory for test execution · ea4ce92a
      libgit2 can now isolate its home directory, and our test runner (by
      default) isolates the home directory. In our CI environment, we want to
      set up some pieces (like ssh configuration) in a fake homedir. Continue
      to do so and propagate that to clar.
      Edward Thomson committed
  6. 04 Nov, 2022 1 commit
  7. 19 Sep, 2022 2 commits
  8. 16 Sep, 2022 1 commit
  9. 23 Feb, 2022 2 commits
  10. 18 Jan, 2022 1 commit
  11. 13 Jan, 2022 4 commits
  12. 30 Aug, 2021 2 commits
  13. 18 Nov, 2020 1 commit
  14. 13 Mar, 2020 1 commit
  15. 07 Feb, 2020 2 commits
  16. 04 Feb, 2020 2 commits
  17. 24 Jan, 2020 3 commits
  18. 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
  19. 24 Jun, 2019 1 commit
  20. 10 Jun, 2019 1 commit
  21. 20 Jan, 2019 1 commit
  22. 19 Jan, 2019 1 commit