Summary: Our valgrind testing is buggy and cumbersome in terms of locating the error. It originates from the fact we accumulate all output for the tests. It is extremely hard to locate the point of error. The communication between valgrind and the script is not sturdy. We are experiencing bugs. Simplifying to stop on first error. Test Plan: Run manually Reviewers: sdong igor CC: leveldb@ Task ID: #6968635 Blame Rev:main
parent
4805fa0eae
commit
628216fc1f
@ -1,20 +0,0 @@ |
||||
#!/bin/bash |
||||
#A shell script for Jenknis to run valgrind on rocksdb tests |
||||
#Returns 0 on success when there are no failed tests |
||||
|
||||
VALGRIND_DIR=build_tools/VALGRIND_LOGS |
||||
make clean |
||||
make -j$(nproc) valgrind_check |
||||
if [ $? -ne 0 ]; then |
||||
cat $VALGRIND_DIR/valgrind_failed_tests |
||||
exit 1 |
||||
fi |
||||
|
||||
NUM_FAILED_TESTS=$((`wc -l $VALGRIND_DIR/valgrind_failed_tests | awk '{print $1}'` - 1)) |
||||
if [ $NUM_FAILED_TESTS -lt 1 ]; then |
||||
echo No tests have valgrind errors |
||||
exit 0 |
||||
else |
||||
cat $VALGRIND_DIR/valgrind_failed_tests |
||||
exit 1 |
||||
fi |
Loading…
Reference in new issue