yugabyte/yugabyte-db

Use the log_path clang sanitizer (ASAN/TSAN/etc.) option to put errors in a separate file

Open

#231 opened on Apr 23, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (1,003 forks)batch import
area/docdbhelp wantedkind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-5018 Putting sanitizer errors in a separate file (with a name that can be matched to the process, e.g. ts-1 or m-2) will allow us to parse / display those warnings more easily and detect test failures based on that.

Contributor guide

Research direction
Investigate how clang sanitizers are currently invoked in the build files (e.g., CMakeLists.txt, Makefile) and add the log path option to separate error outputs per process.
Tech stack
ccpp
Domain
backendbuild systemtesting
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C/C++Clang sanitizersBuild system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55