diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-06-25 08:58:08 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-06-25 08:58:11 -0400 |
| commit | ead6d686eb686d6f3dddaefba9efe9f833d803a7 (patch) | |
| tree | 9b149fa974c067b259493fb7ace867d61c38f6a6 /src | |
| parent | c9d1040d254eedac98ec4a2038742d7b3d45f9ab (diff) | |
| parent | 3f686d1a286f88af7baa17c0c9dc439559a66e81 (diff) | |
Merge #18912: ci: Run fuzz testing test cases (bitcoin-core/qa-assets) under valgrind to catch memory errors
3f686d1a286f88af7baa17c0c9dc439559a66e81 ci: Run fuzz testing test cases (bitcoin-core/qa-assets) under valgrind to catch memory errors (practicalswift)
Pull request description:
Re-introduce the Travis valgrind fuzzing job which was removed by PR #18899. The removal seems to have been made by accident since the removed job does not appear to be the source of the problem the PR set out to fix.
---
Run fuzz testing [test cases (bitcoin-core/qa-assets)](https://github.com/bitcoin-core/qa-assets) under `valgrind`.
This would have caught `util: Avoid potential uninitialized read in FormatISO8601DateTime(int64_t) by checking gmtime_s/gmtime_r return value` (#18162) and similar cases.
This fuzzing job was introduced in #18166.
Top commit has no ACKs.
Tree-SHA512: 6e2681eb0ade6af465c5ea91ac163a337465d2130ec9880ba57a36d9af7c25682734586a32977dc25972d4f78483f339d680ea48c0ae13cf1dfa52b617aae401
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions