3 The regression tests run zstd in many scenarios and ensures that the size of the compressed results doesn't change. This helps us ensure that we don't accidentally regress zstd's compression ratio.
5 These tests get run every night by CircleCI. If the job fails you can read the diff printed by the job to ensure the change isn't a regression. If all is well you can download the `results.csv` artifact and commit the new results. Or you can rebuild it yourself following the instructions below.
7 ## Rebuilding results.csv
9 From the root of the zstd repo run:
12 # Build the zstd binary
16 # Build the regression test binary
21 # Run the regression test
22 ./test --cache data-cache --zstd ../../zstd --output results.csv
24 # Check results.csv to ensure the new results are okay