This depends on tikv/jemalloc#2 , which is a cherry-pick of jemalloc/jemalloc#1604 .
See jemalloc/jemalloc#1605 for details of the bug that this fixes; basically, it makes profiling/sampling fail to work under some conditions. We hit this in practice at Materialize when attempting to switch to tikv/jemallocator.
Signed-off-by: Brennan Vincent <brennan@materialize.com>
- ppc64le is not checked as there is no ppc64le runners.
- valgrind is removed.
- no_std check is removed
Signed-off-by: Jay Lee <BusyJayLee@gmail.com>
As we are going to publish the crate to crates.io, we need a different
name and version. Since native library is upgraded, all versions are
bumpped to 0.4.0. To make it clear which version of jemalloc is used, I
attach a build tag 5.2.1.
And the project are upgraded to 2018 version.
Signed-off-by: Jay Lee <BusyJayLee@gmail.com>
- Remove all cross compilation and reduce supporting platforms
- Remove complicated checks and builds
- Update jemalloc to 5.2.1
- Fixgnzlbg/jemallocator#147
Signed-off-by: Jay Lee <BusyJayLee@gmail.com>
- disable configure verify check
- update configure file and make clippy happy
- check autoconf version
- fix allow_failures
- i686-apple target are not supported now
- use latest travis syntax
- less verbose and allow non-master check fail
Upstream doesn't guarantee configure file matches across platform and
versions. Checking configure file can fail easily
- mute alloc_trait tests
- rich diff
- remove unsupported platform
i686-apple-darwin is removed from nightly and beta.
- make clippy and rustfmt happy
Signed-off-by: Jay Lee <BusyJayLee@gmail.com>
This PR allows automatically fetching the latest jemalloc from
its dev branch by defining the environment variable
`JEMALLOC_SYS_GIT_DEV_BRANCH`. This is useful when debugging
whether certain bugs are already fixed upstream, as well as
for detecting whether upstream changes break our tests.
This PR adds two build jobs that test the dev branch on the
tier-1 x86_64 linux and osx targets.