From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] [RELEASE] LTTng-Tools 2.6.2 - Gaïa
Date: Tue, 19 Apr 2016 14:48:04 -0400 [thread overview]
Message-ID: <CA+jJMxtaHfW6hLPwGc8uYG2Nj6qUgOaz-raWy7dgr2Nq5dx0dQ@mail.gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
Hi all,
Today we are releasing the second bug-fix release of LTTng-Tools 2.6.
This release addresses a number of minor issues listed below.
2016-04-19 lttng-tools 2.6.2 (Bicycle Day)
* Fix: add missing synchronization point for before app test case
* Fix warning when building Python bindings
* Tests: use configured processor count in tracefile count test
* Tests: use configured processor count in snapshot tests
* Tests: Introduce conf_proc_count()
* Test: prevent the spawning of a daemonized sessiond
* Fix: do not print error and bug messages when quiet (-q) is present
* Build: fallback to AC_CHECK_LIBS when looking for popt and uuid
* tests/unit: fix object files' location
* configure.ac: fix static build
* Fix: close indexes when rotating the trace files in mmap mode
* Fix: close indexes when rotating the trace files in splice mode
* Fix: use liburcu flavor header instead of local copy
* Fix: rculfhash should not include specific rcu flavor
* Fix live timer calculation error
As always, please report any issue you may encounter to bugs.lttng.org
or on this mailing list.
Project website: https://lttng.org
Download links:
https://lttng.org/files/lttng-tools/lttng-tools-2.6.2.tar.bz2
GPG sig: https://lttng.org/files/lttng-tools/lttng-tools-2.6.2.tar.bz2.asc
Regards,
Jérémie
--
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2016-04-19 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+jJMxtaHfW6hLPwGc8uYG2Nj6qUgOaz-raWy7dgr2Nq5dx0dQ@mail.gmail.com \
--to=jeremie.galarneau@efficios.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox