1. 07 Feb, 2020 1 commit
    • tests: iterator: fix iterator expecting too few items · 26b71d60
      The testcase iterator::workdir::filesystem_gunk sets up quite a lot of
      directories, which is why it only runs in case GITTEST_INVASIVE_SPEED is
      set in the environment. Because we do not run our default CI with this
      variable, we didn't notice commit 852c83ee (refs: refuse to delete
      HEAD, 2020-01-15) breaking the test as it introduced a new reference to
      the "testrepo" repository.
      
      Fix the oversight by increasing the number of expected iterator items.
      Patrick Steinhardt committed
  2. 15 Jan, 2020 1 commit
    • refs: refuse to delete HEAD · 852c83ee
      This requires adding a new symbolic ref to the testrepo fixture.
      Some of the existing tests attempt to delete HEAD, expecting a different failure. Introduce and use a non-HEAD symbolic ref instead.
      Adjust a few other tests as needed.
      
      Fixes #5357
      Josh Bleecher Snyder committed
  3. 20 Jul, 2019 1 commit
  4. 24 May, 2019 1 commit
  5. 14 Jan, 2019 1 commit
  6. 01 Dec, 2018 1 commit
  7. 03 Nov, 2018 1 commit
    • iterator: optionally hash filesystem iterators · 2b12dcf6
      Optionally hash the contents of files encountered in the filesystem or
      working directory iterators.  This is not expected to be used in
      production code paths, but may allow us to simplify some test contexts.
      
      For working directory iterators, apply filters as appropriate, since we
      have the context able to do it.
      Edward Thomson committed
  8. 10 Jun, 2018 1 commit
  9. 04 May, 2018 1 commit
    • tests: iterator::workdir: fix GCC warning · 1bf57b5a
      Since GCC 8.1, the compiler performs some bounds checking when
      copying static data into arrays with a known size. In one test,
      we print a format string of "%s/sub%02d" into a buffer of 64
      bytes. The input buffer for the first "%s" is bounded to at most
      63 characters, plus four bytes for the static string "/sub" plus
      two more bytes for "%02d". Thus, our target buffer needs to be at
      least 70 bytes in size, including the NUL byte. There seems to be
      a bug in the analysis, though, because GCC will not account for
      the limiting "%02" prefix, treating it as requiring the same
      count of bytes as a "%d".
      
      Thus, we end up at 79 bytes that are required to fix the
      warning. To make it look nicer and less special, we just round
      the buffer size up to 80 bytes.
      Patrick Steinhardt committed
  10. 24 Feb, 2018 1 commit
  11. 03 Jan, 2018 3 commits
    • tests: iterator::workdir: fix reference count in stale test · b8c14499
      The test `iterator::workdir::filesystem_gunk` is usually not executed,
      as it is guarded by the environment variable "GITTEST_INVASIVE_SPEED"
      due to its effects on speed. As such, it has become stale and does not
      account for new references which have meanwhile been added to the
      testrepo, causing it to fail. Fix this by raising the number of expected
      references to 15.
      Patrick Steinhardt committed
    • tests: iterator_helpers: assert number of iterator items · 9aba7636
      When the function `expect_iterator_items` surpasses the number of
      expected items, we simply break the loop. This causes us to trigger an
      assert later on which has message attached, which is annoying when
      trying to locate the root error cause. Instead, directly assert that the
      current count is still smaller or equal to the expected count inside of
      the loop.
      Patrick Steinhardt committed
    • tests: status::worktree: indicate skipped tests on Win32 · 72c28ab0
      Some function bodies of tests which are not applicable to the Win32
      platform are completely #ifdef'd out instead of calling `cl_skip()`.
      This leaves us with no indication that these tests are not being
      executed at all and may thus cause decreased scrutiny when investigating
      skipped tests. Improve the situation by calling `cl_skip()` instead of
      just doing nothing.
      Patrick Steinhardt committed
  12. 13 Feb, 2017 2 commits
  13. 24 Jul, 2016 1 commit
  14. 11 Apr, 2016 1 commit
  15. 02 Apr, 2016 1 commit
  16. 31 Mar, 2016 1 commit
  17. 24 Mar, 2016 6 commits