1. 06 Sep, 2020 2 commits
  2. 21 Jul, 2020 1 commit
    • Oran Agra's avatar
      testsuite may leave servers alive on error (#7549) · 36b94943
      Oran Agra authored
      in cases where you have
      test name {
        start_server {
          start_server {
            assert
          }
        }
      }
      
      the exception will be thrown to the test proc, and the servers are
      supposed to be killed on the way out. but it seems there was always a
      bug of not cleaning the server stack, and recently (#7404) we started
      relying on that stack in order to kill them, so with that bug sometimes
      we would have tried to kill the same server twice, and leave one alive.
      
      luckly, in most cases the pattern is:
      start_server {
        test name {
        }
      }
      36b94943
  3. 10 Jul, 2020 1 commit
    • Oran Agra's avatar
      tests/valgrind: don't use debug restart (#7404) · 69ade873
      Oran Agra authored
      * tests/valgrind: don't use debug restart
      
      DEBUG REATART causes two issues:
      1. it uses execve which replaces the original process and valgrind doesn't
         have a chance to check for errors, so leaks go unreported.
      2. valgrind report invalid calls to close() which we're unable to resolve.
      
      So now the tests use restart_server mechanism in the tests, that terminates
      the old server and starts a new one, new PID, but same stdout, stderr.
      
      since the stderr can contain two or more valgrind report, it is not enough
      to just check for the absence of leaks, we also need to check for some known
      errors, we do both, and fail if we either find an error, or can't find a
      report saying there are no leaks.
      
      other changes:
      - when killing a server that was already terminated we check for leaks too.
      - adding DEBUG LEAK which was used to test it.
      - adding --trace-children to valgrind, although no longer needed.
      - since the stdout contains two or more runs, we need slightly different way
        of checking if the new process is up (explicitly looking for the new PID)
      - move the code that handles --wait-server to happen earlier (before
        watching the startup message in the log), and serve the restarted server too.
      
      * squashme - CR fixes
      69ade873
  4. 26 May, 2020 1 commit
    • Oran Agra's avatar
      tests: each test client work on a distinct port range · e258a1c0
      Oran Agra authored
      apparently when running tests in parallel (the default of --clients 16),
      there's a chance for two tests to use the same port.
      specifically, one test might shutdown a master and still have the
      replica up, and then another test will re-use the port number of master
      for another master, and then that replica will connect to the master of
      the other test.
      
      this can cause a master to count too many full syncs and fail a test if
      we run the tests with --single integration/psync2 --loop --stop
      
      see Probmem 2 in #7314
      e258a1c0
  5. 06 Apr, 2020 1 commit
  6. 11 Mar, 2020 1 commit
  7. 24 Feb, 2020 1 commit
  8. 21 Feb, 2020 2 commits
  9. 07 Oct, 2019 1 commit
    • Yossi Gottlieb's avatar
      TLS: Connections refactoring and TLS support. · b087dd1d
      Yossi Gottlieb authored
      * Introduce a connection abstraction layer for all socket operations and
      integrate it across the code base.
      * Provide an optional TLS connections implementation based on OpenSSL.
      * Pull a newer version of hiredis with TLS support.
      * Tests, redis-cli updates for TLS support.
      b087dd1d
  10. 04 Sep, 2018 1 commit
  11. 26 Jun, 2018 1 commit
    • Oran Agra's avatar
      test suite infra improvements and fix · 751eea24
      Oran Agra authored
      * fail the test (exit code) in case of timeout.
      * add --wait-server to allow attaching a debugger
      * add --dont-clean to keep log files when tests are done
      751eea24
  12. 19 Dec, 2016 1 commit
  13. 01 Oct, 2015 1 commit
  14. 31 Mar, 2015 1 commit
  15. 21 Jan, 2015 1 commit
  16. 28 Nov, 2014 2 commits
    • antirez's avatar
      Test: wait for actual startup in start_server. · fe0d3719
      antirez authored
      start_server now uses return value from Tcl exec to get the server pid,
      however this introduces errors that depend from timing: a lot of the
      testing code base assumed the server to be actually up and running when
      server_start returns.
      
      So the old code that waits to see the pid in the log file was restored.
      fe0d3719
    • antirez's avatar
      Test: try to cleanup still running Redis instances on exit. · bd3a5161
      antirez authored
      It's hard to run the Redis test continuously if it leaks processes on
      exceptions / errors.
      bd3a5161
  17. 29 Sep, 2014 1 commit
  18. 23 May, 2014 1 commit
    • Matt Stancliff's avatar
      Fix test framework to detect proper server PID · 6c16ecaa
      Matt Stancliff authored
      Previously the PID format was:
      [PID] Timestamp
      
      But it recently changed to:
      PID:X Timestamp
      
      The tcl testing framework was grabbing the PID from \[\d+\], but
      that's not valid anymore.
      
      Now we grab the pid from "PID: <PID>" in the part of Redis startup
      output to the right of the ASCII logo.
      6c16ecaa
  19. 07 May, 2014 1 commit
    • antirez's avatar
      Test: handle new osx 'leaks' error. · 088b9ead
      antirez authored
      Sometimes the process is still there but no longer in a state that can
      be checked (after being killed). This used to happen after a call to
      SHUTDOWN NOSAVE in the scripting unit, causing a false positive.
      088b9ead
  20. 25 Mar, 2014 1 commit
  21. 17 Feb, 2014 1 commit
  22. 12 Feb, 2013 1 commit
  23. 03 Dec, 2012 1 commit
    • antirez's avatar
      Test: fixed osx "leaks" support in test. · a18ca736
      antirez authored
      Due to changes in recent releases of osx leaks utility, the osx leak
      detection no longer worked. Now it is fixed in a way that should be
      backward compatible.
      a18ca736
  24. 24 Oct, 2012 1 commit
  25. 17 Apr, 2012 1 commit
  26. 03 Apr, 2012 1 commit
  27. 28 Mar, 2012 1 commit
  28. 24 Mar, 2012 1 commit
  29. 07 Dec, 2011 2 commits
  30. 04 Oct, 2011 1 commit
    • antirez's avatar
      Redis test ports selection made more robust. This prevents the test from... · 24bfb570
      antirez authored
      Redis test ports selection made more robust. This prevents the test from hanging if an already bound port is selected but the TCP server listening to it does not cause a protocol error with a Redis client PING. Also base port moved away from the range near to the Redis Cluster gossip ports.
      24bfb570
  31. 11 Jul, 2011 1 commit
  32. 09 Jul, 2011 1 commit
  33. 06 Jul, 2011 1 commit
  34. 15 Apr, 2011 1 commit
  35. 09 Jan, 2011 1 commit
  36. 03 Jan, 2011 1 commit