Re: [Qemu-devel] [PATCH 0/3] Reduce the number of Valgrind reports in unit tests.

2019-08-13 Thread Andrey Shinkevich
On 13/08/2019 15:05, Paolo Bonzini wrote: > On 13/08/19 14:02, Andrey Shinkevich wrote: >> PINGING... > > I thought I had already said I queued the series? > > Paolo > Thank you Paolo. I am clear now. Andrey >> On 30/07/2019 19:01, Andrey Shinkevich wrote: >>> Running unit tests under the V

Re: [Qemu-devel] [PATCH 0/3] Reduce the number of Valgrind reports in unit tests.

2019-08-13 Thread Paolo Bonzini
On 13/08/19 14:02, Andrey Shinkevich wrote: > PINGING... I thought I had already said I queued the series? Paolo > On 30/07/2019 19:01, Andrey Shinkevich wrote: >> Running unit tests under the Valgrind may help to detect QEMU memory issues >> (suggested by Denis V. Lunev). Some of the Valgrind r

Re: [Qemu-devel] [PATCH 0/3] Reduce the number of Valgrind reports in unit tests.

2019-08-13 Thread Andrey Shinkevich
PINGING... On 30/07/2019 19:01, Andrey Shinkevich wrote: > Running unit tests under the Valgrind may help to detect QEMU memory issues > (suggested by Denis V. Lunev). Some of the Valgrind reports relate to the > unit test code itself. Let's eliminate the detected memory issues to ease > locating

[Qemu-devel] [PATCH 0/3] Reduce the number of Valgrind reports in unit tests.

2019-07-30 Thread Andrey Shinkevich
Running unit tests under the Valgrind may help to detect QEMU memory issues (suggested by Denis V. Lunev). Some of the Valgrind reports relate to the unit test code itself. Let's eliminate the detected memory issues to ease locating critical ones. Andrey Shinkevich (3): test-throttle: Fix uninit