summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel/lttng/lttng-tools
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2018-11-19 15:24:09 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-11-20 10:32:16 +0000
commitaa24e1aaf84a2721fc58b43e458cb94f197f5677 (patch)
tree5de584410162f5f1594d8e4852cc53a5f0b2e4d3 /meta/recipes-kernel/lttng/lttng-tools
parent33a833960897a082d53fbce06e621635173bc5c1 (diff)
downloadpoky-aa24e1aaf84a2721fc58b43e458cb94f197f5677.tar.gz
lttng-tools: Upgrade 2.9.5 -> 2.10.5 and improve ptest
A backported patch was removed. The kmod option changed format in the new version so was adjusted accordingly. The ptest package was improved to resolve failures in the tests/unit/ directory but disabling attempts to rebuild the binaries on target. Various ptest libtool script wrappers are now replaced with real binaries and since the test suite knows about these paths for dymanic libraries, we put links in place for those. A data file needed by one of the tests is also copied in. (From OE-Core rev: fbafcd9a0101a637181d0aa9ec14579309a9bddf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/lttng/lttng-tools')
-rw-r--r--meta/recipes-kernel/lttng/lttng-tools/0001-Allow-multiple-attempts-to-connect-to-relayd.patch43
1 files changed, 0 insertions, 43 deletions
diff --git a/meta/recipes-kernel/lttng/lttng-tools/0001-Allow-multiple-attempts-to-connect-to-relayd.patch b/meta/recipes-kernel/lttng/lttng-tools/0001-Allow-multiple-attempts-to-connect-to-relayd.patch
deleted file mode 100644
index 62a0978592..0000000000
--- a/meta/recipes-kernel/lttng/lttng-tools/0001-Allow-multiple-attempts-to-connect-to-relayd.patch
+++ /dev/null
@@ -1,43 +0,0 @@
1From 70eff899104b86bae02862927c76caaef5de5d3c Mon Sep 17 00:00:00 2001
2From: Mikael Beckius <mikael.beckius@windriver.com>
3Date: Thu, 7 May 2015 16:14:25 +0200
4Subject: [PATCH] Allow multiple attempts to connect to relayd.
5
6It is unclear why a session needs to be made
7unusable after a failure to connect to relayd
8since a check for a relayd connection is
9always made before a session can be configured.
10
11The behaviour was introduced in:
12d9078d0c000d04d49c599a72c1a725026b636ec0
13
14Signed-off-by: Mikael Beckius <mikael.beckius@windriver.com>
15[ The context has moved, adjust the hunk accordingly ]
16Signed-off-by: He Zhe <zhe.he@windriver.com>
17Upstream-Status: Pending
18---
19 src/bin/lttng-sessiond/cmd.c | 8 --------
20 1 file changed, 8 deletions(-)
21
22diff --git a/src/bin/lttng-sessiond/cmd.c b/src/bin/lttng-sessiond/cmd.c
23index 73b4ce3..36f62ee 100644
24--- a/src/bin/lttng-sessiond/cmd.c
25+++ b/src/bin/lttng-sessiond/cmd.c
26@@ -689,14 +689,6 @@ close_sock:
27 free(rsock);
28
29 error:
30- if (ret != LTTNG_OK) {
31- /*
32- * The consumer output for this session should not be used anymore
33- * since the relayd connection failed thus making any tracing or/and
34- * streaming not usable.
35- */
36- consumer->enabled = 0;
37- }
38 return ret;
39 }
40
41--
421.7.9.5
43