-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run asan in CI and stabilize write barrier test #120
Conversation
Crossbeam channel will definitely cause race condition, as a feature. So this won’t work. |
Signed-off-by: tabokie <xy.tao@outlook.com>
Signed-off-by: tabokie <xy.tao@outlook.com>
FYI tikv/agatedb#51 |
Thanks for the pointer, but crossbeam is actually not needed anymore after #77. Anyhow, sanitizer currently can't build, seemingly caused by https://github.com/HdrHistogram/HdrHistogram_rust. I might look into that later. |
Signed-off-by: tabokie <xy.tao@outlook.com>
Signed-off-by: tabokie <xy.tao@outlook.com>
BTW, running ASAN also requires |
Signed-off-by: tabokie <xy.tao@outlook.com>
Signed-off-by: tabokie xy.tao@outlook.com
Run ASAN in linux CI pipeline. The write barrier test is unstable when ran under asan/miri, fixing it. Also some housekeeping work: remove build step in CI, remove useless code.
TSAN still can't run because we use crossbeam channel for parallel recovery.