From: Claudio André
Sanitizers are based on compile-time instrumentation. They are available
in gcc and clang for a range of supported operation systems and
platforms. More info at: https://github.com/google/sanitizers
The address sanitizer finds bugs related to addressing memory: use after
free
From: Claudio André
It is possible to test libvirt using other distros in Travis via Docker;
including (but not limited to) Fedora and Ubuntu.
---
https://travis-ci.org/claudioandre/libvirt/builds/237995646
.travis.yml| 19 ++---
tests/travis-ci.sh | 80 +
From: Claudio André
It is possible to test libvirt using other distros in Travis via Docker;
including (but not limited to) Fedora and Ubuntu.
---
See it in action at https://travis-ci.org/claudioandre/libvirt/builds/237687907
.travis.yml| 23 ++
tests/travis-ci.sh | 70
From: Claudio André
Sanitizers are based on compile-time instrumentation. They are available in gcc
and clang for a range of supported operation systems and platforms. More info
at: https://github.com/google/sanitizers
The address sanitizer finds bugs related to addressing memory: use after fr
From: Claudio André
It is possible to test libvirt using other distros in Travis via Docker;
including (but not limited to) Fedora and Ubuntu.
---
Notes:
* see it working at: https://travis-ci.org/claudioandre/libvirt/builds/237015534
* now, I introduced an error:
https://travis-ci.org/claudioa
From: Claudio André
Disclosure the content of the 'test-suite.log' file (if available) in case of
failures inside Travis-CI. This is needed to understand what happened and to
provide hints about the proper fix (if applicable).
---
.travis.yml | 8
1 file changed, 8 insertions(+)
diff
From: Claudio André
It builds the code coverage report and uploads the coverage data to a web
service in order to allow to track libvirt's code coverage over time.
---
.travis.yml | 11 ++-
README.md | 1 +
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/.travis.yml b/
From: Claudio André
*** ***
NOTE: In order to add links to demonstrate it working, I'm using a cover letter
for only 1 patch. Sorry about this!
It is possible to see how it behaves, just access:
- https://gist.github.com/claudioandre/60b262ff8c110133c0a94d5f0ce2362c
- https://coveralls.io/buil