1. 10 Sep, 2020 2 commits
    • Oran Agra's avatar
      fix broken cluster/sentinel tests by recent commit (#7752) · a227bc80
      Oran Agra authored
      2b998de4 added a file for stderr to keep valgrind log but i forgot to
      add a similar thing when valgrind isn't being used.
      the result is that `glob */err.txt` fails.
      
      (cherry picked from commit 42ba7a1b)
      a227bc80
    • Oran Agra's avatar
      Improve valgrind support for cluster tests (#7725) · d410dc31
      Oran Agra authored
      - redirect valgrind reports to a dedicated file rather than console
      - try to avoid killing instances with SIGKILL so that we get the memory
        leak report (killing with SIGTERM before resorting to SIGKILL)
      - search for valgrind reports when done, print them and fail the tests
      - add --dont-clean option to keep the logs on exit
      - fix exit error code when crash is found (would have exited with 0)
      
      changes that affect the normal redis test suite:
      - refactor check_valgrind_errors into two functions one to search and
        one to report
      - move the search half into util.tcl to serve the cluster tests too
      - ignore "address range perms" valgrind warnings which seem non relevant.
      
      (cherry picked from commit 2b998de4)
      d410dc31
  2. 01 Sep, 2020 2 commits
  3. 20 Jul, 2020 1 commit
    • WuYunlong's avatar
      Fix out of update help info in tcl tests. (#7516) · 4780cc5e
      WuYunlong authored
      Before this commit, the output of "./runtest-cluster --help" is incorrect.
      After this commit, the format of the following 3 output is consistent:
      ./runtest --help
      ./runtest-cluster --help
      ./runtest-sentinel --help
      
      (cherry picked from commit 8128d397)
      4780cc5e
  4. 28 May, 2020 1 commit
    • Oran Agra's avatar
      tests: each test client work on a distinct port range · a2ae4635
      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
      a2ae4635
  5. 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
  6. 13 Aug, 2017 1 commit
  7. 15 Jan, 2016 2 commits
  8. 02 Jan, 2016 1 commit
  9. 29 Dec, 2015 1 commit
  10. 30 Mar, 2015 1 commit
  11. 22 Jan, 2015 1 commit
  12. 21 Jan, 2015 4 commits
  13. 29 Sep, 2014 1 commit
  14. 30 Jun, 2014 1 commit
  15. 18 Jun, 2014 1 commit
  16. 10 Jun, 2014 1 commit
  17. 19 May, 2014 1 commit
  18. 29 Apr, 2014 1 commit
  19. 24 Apr, 2014 2 commits
  20. 18 Mar, 2014 2 commits
  21. 04 Mar, 2014 4 commits
  22. 03 Mar, 2014 1 commit
  23. 25 Feb, 2014 2 commits
  24. 23 Feb, 2014 2 commits
  25. 22 Feb, 2014 1 commit
    • antirez's avatar
      Sentinel test: framework improved and conf-update unit added. · 8c254415
      antirez authored
      It is now possible to kill and restart sentinel or redis instances for
      more real-world testing.
      
      The 01 unit tests the capability of Sentinel to update the configuration
      of Sentinels rejoining the cluster, however the test is pretty trivial
      and more tests should be added.
      8c254415
  26. 20 Feb, 2014 2 commits