You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Suraj Acharya (JIRA)" <ji...@apache.org> on 2017/05/14 23:15:04 UTC
[jira] [Updated] (AVRO-2026) Incorporate valgrind memory testing
for C
[ https://issues.apache.org/jira/browse/AVRO-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suraj Acharya updated AVRO-2026:
--------------------------------
Fix Version/s: (was: 1.8.2)
1.8.3
> Incorporate valgrind memory testing for C
> -----------------------------------------
>
> Key: AVRO-2026
> URL: https://issues.apache.org/jira/browse/AVRO-2026
> Project: Avro
> Issue Type: Improvement
> Components: c
> Reporter: John Gill
> Fix For: 1.8.3
>
> Attachments: AVRO-2026.patch
>
>
> With the work done for AVRO-1167 & AVRO-766 in identifying memory leaks decided to make it a standard part of the testing framework. This issue requires https://github.com/apache/avro/pull/218 otherwise test_avro_schema and test_avro_values fail due to to avro_schema_copy calls.
> Adding valgrind tool to the docker container
> Adding valgrind to CMakeLists.txt to optionally do valgrind testing if the tool is found
> Cleaning up existing tests that were failing due to not properly cleaning up memory
> Lastly, as part of ./build.sh test for lang/c do not remove the build/c directory. The memcheck output is kept so that memory leak issues can be reviewed and addressed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)