summaryrefslogtreecommitdiff
path: root/scripts
AgeCommit message (Collapse)Author
2019-04-15Safety checks: Run tests by defaultDavid Goldblatt
2019-02-06Add --disable-libdl to travis.Qi Wang
2018-10-17Test smallocx on Travis-CIgnzlbg
This commit updates the gen_travis script with a new build bot that covers the experimental `smallocx` API and updates the travis CI script to test this API under travis.
2018-08-13Add valgrind build bots to CIgnzlbg
This commit adds two build-bots to CI that test the release builds of jemalloc on linux and macOS under valgrind. The macOS build is not enabled because valgrind reports errors about reads of uninitialized memory in some tests and segfaults in others.
2018-08-09FreeBSD build changes and allow to run the tests.David Carlier
2018-07-17Test that .travis.yml has been produced by gen_travis.py on CIgnzlbg
This commits checks on Travis-CI that the current `.travis.yml` file equals the output of the `gen_travis.py` script, and updated the `.travis.yml` file accordingly.
2018-07-17Simplify output of gen_travis.py scriptgnzlbg
This commit simplifies the output of the `gen_travis.py` script by reusing addons. The `.travis.yml` script is updated to reflect these changes.
2018-05-08run_tests.sh: Don't test large vaddr with -m32.David T. Goldblatt
2018-05-04run_tests.sh: Test --with-lg-vaddr.David Goldblatt
2017-07-31Remove a redundant '--with-malloc-conf=tcache:false' from gen_run_tests.pyDavid Goldblatt
This is already tested via its inclusion in possible_malloc_conf_opts.
2017-06-01Test with background_thread:true.Jason Evans
Add testing for background_thread:true, and condition a xallocx() --> rallocx() escalation assertion to allow for spurious in-place rallocx() following xallocx() failure.
2017-05-31Clean source directory before building tests in object directories.Jason Evans
2017-05-26Fix run_tests to avoid percpu_arena on !Linux.Jason Evans
2017-05-24Refactor run_tests to increase parallelism.Jason Evans
Rather than relying on parallel make to build individual configurations one at a time, use xargs to build multiple configurations in parallel. This allows the configure scripts to run in parallel. On a 14-core system (28 hyperthreads), this increases average CPU utilization from ~20% to ~90%.
2017-05-23Disable percpu_arena by default.Jason Evans
2017-05-23Add dss:primary testing.Jason Evans
Generalize the run_tests.sh and .travis.yml test generation to handle combinations of arguments to the --with-malloc-conf configure option, and merge "dss:primary" into the existing "tcache:false" testing.
2017-05-11Specify -Werror for run_tests builds.Jason Evans
2017-04-21Remove --disable-tcache.Jason Evans
Simplify configuration by removing the --disable-tcache option, but replace the testing for that configuration with --with-malloc-conf=tcache:false. Fix the thread.arena and thread.tcache.flush mallctls to work correctly if tcache is disabled. This partially resolves #580.
2017-04-10Turn on -Werror for travis CI buildsDavid Goldblatt
2017-02-28Dodge 32-bit-clang-specific backtracing failure.Jason Evans
This disables run_tests.sh configurations that use the combination of 32-bit clang and heap profiling.
2017-01-30Introduce scripts to run all possible testsDavid Goldblatt
In 6e7d0890 we added better travis continuous integration tests. This is nice, but has two problems: - We run only a subset of interesting tests. - The travis builds can take hours to give us back results (especially on OS X). This adds scripts/gen_run_tests.py, and its output, run_tests.sh, which builds and runs a larger portion of possible configurations on the local machine. While a travis run takes several hours to complete , I can run these scripts on my (OS X) latop and (Linux) devserve, and get a more exhaustive set of results back in around 10 minutes.
2017-01-26Beef up travis CI integration testingDavid Goldblatt
Introduces gen_travis.py, which generates .travis.yml, and updates .travis.yml to be the generated version. The travis build matrix approach doesn't play well with mixing and matching various different environment settings, so we generate every build explicitly, rather than letting them do it for us. To avoid abusing travis resources (and save us time waiting for CI results), we don't test every possible combination of options; we only check up to 2 unusual settings at a time.