Re: [lttng-dev] [PATCH lttng-tools 1/1] Fix: uninitialized return value on error path

2017-08-03 Thread Jérémie Galarneau
Merged in master, stable-2.10, stable-2.9 and stable-2.8. Thanks! Jérémie On 2 August 2017 at 11:34, Mathieu Desnoyers wrote: > Found by Coverity: > > *** CID 1378810: Uninitialized variables (UNINIT) > /src/bin/lttng-sessiond/context.c: 73 in add_kctx_all_channels() > > Signed-off-by: Mathieu

Re: [lttng-dev] [PATCH lttng-tools] Typo: occured -> occurred

2017-08-03 Thread Jérémie Galarneau
Merged in master and stable-2.10, thanks! Jérémie On 2 August 2017 at 14:26, Michael Jeanson wrote: > Signed-off-by: Michael Jeanson > --- > src/bin/lttng-sessiond/notification-thread-events.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/bin/lttng-sessiond/notif

[lttng-dev] [RELEASE] LTTng-Tools 2.10.1 - KeKriek

2017-08-03 Thread Jérémie Galarneau
Hi all, Today we are releasing the first bug-fix release of LTTng-Tools 2.10 - KeKriek. This release addresses a number of issues listed below. 2017-08-03 lttng-tools 2.10.1 (Watermelon Day) * Typo: occured -> occurred * Fix: uninitialized return value on error path * Fix:

[lttng-dev] [RELEASE] LTTng-Tools 2.8.8 - Isseki Nicho (End of Life)

2017-08-03 Thread Jérémie Galarneau
Hi all, Today we are releasing the eighth and final bug-fix release of LTTng-Tools 2.8 - Isseki Nicho as it has now reached end of life. This release addresses a number of issues listed below. 2017-08-03 lttng-tools 2.8.8 (Watermelon Day) * Fix: uninitialized return value on error path

[lttng-dev] [RELEASE] LTTng-Tools 2.9.6 - Joannès

2017-08-03 Thread Jérémie Galarneau
Hi all, Today we are releasing the sixth bug-fix release of LTTng-Tools 2.9 - Joannès. This release addresses a number of issues listed below. 2017-08-03 lttng-tools 2.9.6 (Watermelon Day) * Fix: uninitialized return value on error path * Fix: ensure kernel context is in a list be

[lttng-dev] babeltrace tests (master/2.0)

2017-08-03 Thread Nathan Lynch
How is the babeltrace test suite on the master and stable-2.0 branches intended to be used? Effectively there are four test suites, one for each definition of TESTS in the tests/ directory. If one of them has a failure, 'make check' will not proceed to the next unless the -k/--keep-going flag is