summaryrefslogtreecommitdiff
path: root/src/crc64.h
Commit message (Collapse)AuthorAgeFilesLines
* Add --large-memory flag for REDIS_TEST to enable tests that consume more ↵sundb2021-11-161-1/+1
| | | | | than 100mb (#9784) This is a preparation step in order to add a new test in quicklist.c see #9776
* Add run all test support with define REDIS_TEST (#8570)sundb2021-03-101-1/+1
| | | | | | | | | | | | 1. Add `redis-server test all` support to run all tests. 2. Add redis test to daily ci. 3. Add `--accurate` option to run slow tests for more iterations (so that by default we run less cycles (shorter time, and less prints). 4. Move dict benchmark to REDIS_TEST. 5. fix some leaks in tests 6. make quicklist tests run on a specific fill set of options rather than huge ranges 7. move some prints in quicklist test outside their loops to reduce prints 8. removing sds.h from dict.c since it is now used in both redis-server and redis-cli (uses hiredis sds)
* Implemented CRC64 based on slice by 4Madelyn Olson2020-04-241-0/+1
|
* Allow all code tests to run using Redis argsMatt Stancliff2014-12-231-0/+4
| | | | | | | | | | | | | | | | | | | | | Previously, many files had individual main() functions for testing, but each required being compiled with their own testing flags. That gets difficult when you have 8 different flags you need to set just to run all tests (plus, some test files required other files to be compiled aaginst them, and it seems some didn't build at all without including the rest of Redis). Now all individual test main() funcions are renamed to a test function for the file itself and one global REDIS_TEST define enables testing across the entire codebase. Tests can now be run with: - `./redis-server test <test>` e.g. ./redis-server test ziplist If REDIS_TEST is not defined, then no tests get included and no tests are included in the final redis-server binary.
* Introduced the Build ID in INFO and --version output.antirez2012-11-291-0/+8
The idea is to be able to identify a build in a unique way, so for instance after a bug report we can recognize that the build is the one of a popular Linux distribution and perform the debugging in the same environment.