PASS: tools/filtering/test_invalid_filter 96 - Enable lttng event with filtering and invalid filter FAIL: tools/filtering/test_invalid_filter 97 - Destroy session filter-invalid FAIL: tools/filtering/test_invalid_filter 98 - Create session filter-invalid in -o /var/tmp/portage/dev-util/lttng-tools-2.13.0/temp/tmp.test_filtering_invalid_filters_trace_path.fEG3aZ FAIL: tools/channel/test_channel 14 - No session daemon to kill ERROR: tools/channel/test_channel - exited with status 3 Error: the following LTTng processes were detected running on the system: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-j4_test_debug-20220211-232930 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): /usr/lib/llvm/13 13.0.1 Python 3.9.10 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.58.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JRE 11.0.14_p9 [openjdk-jre-bin-11] Available Java Virtual Machines: [1] openjdk-jre-bin-11 The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: [1] php7.4 [2] php8.0 [3] php8.1 * HEAD of ::gentoo commit d05c9b54096d2a7c4847a7363d68768da404fc6b Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Feb 14 12:22:06 2022 +0000 2022-02-14 12:22:05 UTC emerge -qpvO dev-util/lttng-tools [ebuild N ] dev-util/lttng-tools-2.13.0 USE="ust"
Created attachment 765087 [details] emerge-info.txt
Created attachment 765088 [details] dev-util:lttng-tools-2.13.0:20220214-141828.log.bz2
Created attachment 765089 [details] emerge-history.txt
Created attachment 765090 [details] environment
Created attachment 765091 [details] etc.portage.tar.bz2
Created attachment 765092 [details] logs.tar.bz2
Created attachment 765093 [details] temp.tar.bz2
*** This bug has been marked as a duplicate of bug 803197 ***