All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>,
	Francis Deslauriers <francis.deslauriers@efficios.com>,
	wangmy <wangmy@fujitsu.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] lttng-tools: upgrade 2.13.4 -> 2.13.6
Date: Wed, 4 May 2022 18:51:40 +0200	[thread overview]
Message-ID: <CANNYZj9oYY8pjcyAyLPJJYpivUaxDpBOxGh79cu239s0uDNryg@mail.gmail.com> (raw)
In-Reply-To: <16EBF18662E1746B.16118@lists.openembedded.org>

The issue was that we used a stripped binary where a non-stripped one
is expected. I have corrected this, so the problem was on our side.
Version update patch will be coming in a few.

Alex

On Wed, 4 May 2022 at 17:47, Alexander Kanavin via
lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
wrote:
>
> I have fixed the test_userspace_probe fails, and obtained slightly
> more detailed logs for the test_callstack:
>
> not ok 11 - Validate userspace callstack
> FAIL: kernel/test_callstack 11 - Validate userspace callstack
> #   Failed test 'Validate userspace callstack'
> #   in ./kernel/test_callstack:test_user_callstack() at line 80.
> # Kernel callstack test
>
> Line 80 in ./tests/regression/kernel/test_callstack is:
>
>         "$BABELTRACE_BIN" "$TRACE_PATH" | grep $EVENT_NAME |
> ./"$PARSE_CALLSTACK" --user "$TEST_APP_USERSPACE" $USER_CS_EXPECTED
>         ok $? "Validate userspace callstack"
>
> I have obtained the failing TRACE_PATH output, and attached it to this
> upstream bug:
> https://bugs.lttng.org/issues/1353
>
> To unblock the update I'll add a patch that disables the failing test.
>
> Alex
>
>
> On Wed, 6 Apr 2022 at 14:35, Alexandre Belloni via
> lists.openembedded.org
> <alexandre.belloni=bootlin.com@lists.openembedded.org> wrote:
> >
> > Hello,
> >
> > Last time I tried that, we got new ptest failures:
> >
> > {'lttng-tools': ['kernel/test_callstack_11_-_Validate_userspace_callstack',
> >                  'kernel/test_userspace_probe_94_-_Enable_kernel_userspace_probe_event_for_session_test_userprobe_elf_cxx_function',
> >                  'kernel/test_userspace_probe_95_-_Start_tracing_for_session_test_userprobe_elf_cxx_function',
> >                  'kernel/test_userspace_probe_96_-_Stop_lttng_tracing_for_session_test_userprobe_elf_cxx_function',
> >                  'kernel/test_userspace_probe_97_-_Validate_trace_for_event_userspace_probe_test_event',
> >                  'kernel/test_userspace_probe_100_-_Enable_kernel_userspace_probe_event_for_session_test_userprobe_elf_cxx_method',
> >                  'kernel/test_userspace_probe_101_-_Start_tracing_for_session_test_userprobe_elf_cxx_method',
> >                  'kernel/test_userspace_probe_102_-_Stop_lttng_tracing_for_session_test_userprobe_elf_cxx_method',
> >                  'kernel/test_userspace_probe_103_-_Validate_trace_for_event_userspace_probe_test_event']}
> >
> > Did you have a look at and fix those?
> >
> > On 04/04/2022 02:43:12+0800, wangmy wrote:
> > > Changelog:
> > > =========
> > > Fix: hide symbols erroneously exported in 2.13.5
> > >
> > > Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> > > ---
> > >  .../lttng/{lttng-tools_2.13.4.bb => lttng-tools_2.13.6.bb}      | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >  rename meta/recipes-kernel/lttng/{lttng-tools_2.13.4.bb => lttng-tools_2.13.6.bb} (98%)
> > >
> > > diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb b/meta/recipes-kernel/lttng/lttng-tools_2.13.6.bb
> > > similarity index 98%
> > > rename from meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
> > > rename to meta/recipes-kernel/lttng/lttng-tools_2.13.6.bb
> > > index 0ea4da05ce..d40d0a2dd0 100644
> > > --- a/meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
> > > +++ b/meta/recipes-kernel/lttng/lttng-tools_2.13.6.bb
> > > @@ -39,7 +39,7 @@ SRC_URI = "https://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \
> > >             file://disable-tests.patch \
> > >             "
> > >
> > > -SRC_URI[sha256sum] = "565f3102410a53d484f4c8ff517978f1dc59f67f9d16f872f4357f3ca12200f6"
> > > +SRC_URI[sha256sum] = "1d52d249437b3f7ba23a45a22c3e26dde006a5da10e96753952084a98e0523e3"
> > >
> > >  inherit autotools ptest pkgconfig useradd python3-dir manpages systemd
> > >
> > > --
> > > 2.25.1
> > >
> >
> > >
> > >
> > >
> >
> >
> > --
> > Alexandre Belloni, co-owner and COO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
> >
> >
> >
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#165223): https://lists.openembedded.org/g/openembedded-core/message/165223
> Mute This Topic: https://lists.openembedded.org/mt/90287422/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


      parent reply	other threads:[~2022-05-04 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 18:43 [OE-core] [PATCH] freetype: upgrade 2.11.1 -> 2.12.0 Wang Mingyu
2022-04-03 18:43 ` [OE-core] [PATCH] ghostscript: upgrade 9.55.0 -> 9.56.1 Wang Mingyu
2022-04-03 18:43 ` [OE-core] [PATCH] libsoup: upgrade 3.0.5 -> 3.0.6 Wang Mingyu
2022-04-03 18:43 ` [OE-core] [PATCH] libx11: upgrade 1.7.3.1 -> 1.7.5 Wang Mingyu
2022-04-03 18:43 ` [OE-core] [PATCH] lttng-tools: upgrade 2.13.4 -> 2.13.6 Wang Mingyu
2022-04-06 12:34   ` Alexandre Belloni
2022-04-06 13:18     ` wangmy
2022-05-04 15:47     ` Alexander Kanavin
     [not found]     ` <16EBF18662E1746B.16118@lists.openembedded.org>
2022-05-04 16:51       ` Alexander Kanavin [this message]

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=CANNYZj9oYY8pjcyAyLPJJYpivUaxDpBOxGh79cu239s0uDNryg@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=francis.deslauriers@efficios.com \
    --cc=jonathan.rajotte-julien@efficios.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wangmy@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.