From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org
Cc: linux-trace-users@vger.kernel.org,
diamon-discuss@lists.linuxfoundation.org
Subject: [RELEASE] LTTng-tools 2.14.2 - Orbitales
Date: Fri, 5 Jun 2026 15:33:54 -0400 [thread overview]
Message-ID: <aiMkot_alZCgDpSC@efficios.com> (raw)
Hi all,
We have just released the second bug-fix release of LTTng-tools 2.14 -
Orbitales. This release addresses a number of issues listed below.
2026-06-05 lttng-tools 2.14.2 (National Fish and Chip Day)
* sessiond: Relax CTF 1.8 TSDL identifier validation
* tests: Exclude `.tmp_new_chunk` from rotation trace size calculation
* Fix: consumerd: silence -Wstringop-truncation warnings
* Fix: tests: use portable format specifier for int64_t in tap
* Fix: Include 32-bit kernel trace expect file in dist
* build: Fix api-doc help string indentation
* build: Fix enable-werror help string indentation
* Fix: sessiond: abort when loading an agent session configuration
* Fix: relayd: wrong session id used in trace chunk existence check
* Fix: lttng: truncated session name when it contains spaces
* Fix: common: remove ambiguous operator[] from c_string_view
* common: Split CPU mask parsing from reading
* Fix: parsing CPU mask with no separators
* Fix: common: Improve cpu mask error checking
* common: Escape newlines when printing CPU mask
* sessiond: Fix: Deadlock when handling notification overflow
* tests: add test_condition to the unit test list
* tests: add notification/test_rotation to the regression test list
* tests: Fix rotation notification test when tmpdir contains symlink
* Fix: tests: race in rotation notification test
* Fix: tests: undefined CHANNEL_NAME in rotation notification test
* Fix: relayd: live viewer reads wrong chunk after per-PID clear
* Fix: consumerd: pause testpoint not re-evaluated after poll()
* Fix: tests: consumer pause testpoint FIFO EOF mishandled as error
* Fix: tests: serial runner produces empty log files for hanging tests
* Fix: common: uri_compare compares uninitialized union tail
* doc: lttng-view(1): remove non-existent '--session' option
* lttng: handle popt parsing errors
* fix: '-Wsuggest-override' only valid for C++ warnings
* Fix: handle failures to find pid cmdline
* Fix: common: lockfile fd leaks into consumerd via fork+exec
* Fix: sessiond: default kernel probe list missing 9p and dma-fence
* tests: fix: lttng-sessiond abort when using libkmod
* Fix: common: lttng client abort when serializing rotate-session action
* Fix: common: stop-session action serialized as start-session in MI
* Fix: common: MI XSD names start/stop-session actions without "_session"
* Fix: common: MI XSD rejects add-context per-context success element
* Fix: common: MI XSD names snapshot record action "record-output"
* Fix: common: enable-event MI emits duplicate exclusions element
As always, please report any issue you may encounter to bugs.lttng.org
or on this mailing list.
Project website: https://lttng.org
Download link:
https://lttng.org/files/lttng-tools/lttng-tools-2.14.2.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.14.2.tar.bz2.asc
reply other threads:[~2026-06-05 19:33 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=aiMkot_alZCgDpSC@efficios.com \
--to=jeremie.galarneau@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
/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