From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>,
Victor Kamensky <kamensky@cisco.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] systemtap: 3.3 -> 4.0
Date: Tue, 16 Oct 2018 10:54:54 +0100 [thread overview]
Message-ID: <9f182627633f75c8383901510cc11e4b87349084.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LYWG7O+VryaFi9r4kc5JagPtuynWHi9gV6nV+cLPUw+SQ@mail.gmail.com>
On Tue, 2018-10-16 at 10:27 +0100, Burton, Ross wrote:
> On Mon, 15 Oct 2018 at 19:22, Victor Kamensky <kamensky@cisco.com>
> wrote:
> > Upgrade systemtap from 3.3 to 4.0: Removed backported patch.
>
> WARNING: systemtap-4.0-r0 do_package_qa: QA Issue: systemtap:
> /systemtap/etc/stap-exporter/EXAMPLE is owned by uid 1000, which is
> the same as the user running bitbake. This may be due to host
> contamination
> systemtap: /systemtap/etc/stap-exporter/EXAMPLE_NOERROR is owned by
> uid 1000, which is the same as the user running bitbake. This may be
> due to host contamination
> systemtap: /systemtap/etc/stap-exporter/errno.stp is owned by uid
> 1000, which is the same as the user running bitbake. This may be due
> to host contamination
> systemtap: /systemtap/etc/stap-exporter/syscalllatency.stp is owned
> by
> uid 1000, which is the same as the user running bitbake. This may be
> due to host contamination
> systemtap: /systemtap/etc/stap-exporter/timeout.stp is owned by uid
> 1000, which is the same as the user running bitbake. This may be due
> to host contamination
> systemtap: /systemtap/etc/stap-exporter/topsys.stp is owned by uid
> 1000, which is the same as the user running bitbake. This may be due
> to host contamination [host-user-contaminated]
There are also other issues from the addition of systemd unit files in
4.0. I've a patch in -next which tweaks both issues which I'll put in
for testing.
Cheers,
Richard
next prev parent reply other threads:[~2018-10-16 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 18:21 [PATCH] systemtap: 3.3 -> 4.0 Victor Kamensky
2018-10-15 21:02 ` Randy MacLeod
2018-10-16 3:54 ` Victor Kamensky
2018-10-16 9:27 ` Burton, Ross
2018-10-16 9:54 ` Richard Purdie [this message]
2018-10-17 5:56 ` Victor Kamensky
2018-10-17 11:59 ` richard.purdie
2018-10-17 14:50 ` Martin Jansa
2018-10-17 15:07 ` richard.purdie
2018-10-17 19:01 ` Martin Jansa
2018-10-17 19:03 ` [PATCH] systemtap: fix QA issue Martin Jansa
2018-10-17 20:21 ` [PATCH] systemtap: 3.3 -> 4.0 Victor Kamensky
2018-10-26 3:37 ` Victor Kamensky
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=9f182627633f75c8383901510cc11e4b87349084.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kamensky@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.