Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.28.rc2.
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
From: Chen Qi
This patch is to ensure recipes get rebuilt correctly and avoid
incorrect sstate cache reuse when toggling multilib.
The following steps show one example of such incorrect sstate cache reuse.
1. enable multilib && bitbake -c populate_sdk
2. disable multilib && bitbake -c
From: Chen Qi
The gcc_multilib_setup function is a function that is run at the
do_configure step, so it's counted into the signature computation.
The MULTILIB_VARIANTS this function uses is also extracted to be
taken into consideration. After the change of setting MULTILIB_VARIANTS
explictly
Hi，Alex
Thank you very much!
I will try it.
Best Regards.
Qiu Tingting
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187846):
https://lists.openembedded.org/g/openembedded-core/message/187846
Mute This Topic:
Consolekit is not needed for systemd and getting it installed by default
can be disturbing.
Signed-off-by: Markus Volk
---
meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
On Mon, 18 Sept 2023 at 20:46, Michael Opdenacker
wrote:
> Ah, right, I should have paid attention to the file name.
> I could reproduce it too.
>
> Thanks a lot Alex :)
> Michael.
I think this backport should help:
On 18.09.23 at 19:16, Alexander Kanavin wrote:
On Mon, 18 Sept 2023 at 18:28, Michael Opdenacker via
lists.openembedded.org
wrote:
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *alsa-lib* to *1.2.10* has
Failed(do_compile).
On 18 Sep 2023, at 18:50, Martin Jansa wrote:
>
> On Mon, Sep 18, 2023 at 7:21 PM Steve Sakoman wrote:
> On Mon, Sep 18, 2023 at 7:10 AM Martin Jansa wrote:
> >
> > I've intentionally sent it only for mickledore as the gcc version in
> > kirkstone and dunfell isn't affected by this (at least
On Mon, Sep 18, 2023 at 7:21 PM Steve Sakoman wrote:
> On Mon, Sep 18, 2023 at 7:10 AM Martin Jansa
> wrote:
> >
> > I've intentionally sent it only for mickledore as the gcc version in
> kirkstone and dunfell isn't affected by this (at least my reproducer isn't).
>
> So, just to clarify, is it
On Mon, Sep 18, 2023 at 7:10 AM Martin Jansa wrote:
>
> I've intentionally sent it only for mickledore as the gcc version in
> kirkstone and dunfell isn't affected by this (at least my reproducer isn't).
So, just to clarify, is it OK to take the CVE-2023-4039.patch for
kirkstone and dunfell?
On Mon, 18 Sept 2023 at 18:28, Michael Opdenacker via
lists.openembedded.org
wrote:
> > this email is a notification from the Auto Upgrade Helper
> > that the automatic attempt to upgrade the recipe *alsa-lib* to *1.2.10* has
> > Failed(do_compile).
> >
> > Detailed error information:
> >
> >
I've intentionally sent it only for mickledore as the gcc version in
kirkstone and dunfell isn't affected by this (at least my reproducer isn't).
On Mon, Sep 18, 2023 at 6:42 PM Steve Sakoman wrote:
> On Mon, Sep 18, 2023 at 6:08 AM Ross Burton wrote:
> >
> > On 18 Sep 2023, at 16:48, Steve
On Mon, Sep 18, 2023 at 6:08 AM Ross Burton wrote:
>
> On 18 Sep 2023, at 16:48, Steve Sakoman wrote:
> >
> > The CVE-2023-4039.patch was also submitted for kirkstone and dunfell.
> > Should I attempt to cherry-pick this fix for those branches too?
>
> The bug says that the patch only applies
Greetings,
On 15.09.23 at 20:59, Auto Upgrade Helper wrote:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *alsa-lib* to *1.2.10* has
Failed(do_compile).
Detailed error information:
do_compile failed
Ouch, as far as I am
On 18 Sep 2023, at 16:48, Steve Sakoman wrote:
>
> The CVE-2023-4039.patch was also submitted for kirkstone and dunfell.
> Should I attempt to cherry-pick this fix for those branches too?
The bug says that the patch only applies cleaning to GCC 12/13, I’m seeking
clarification as to whether
The CVE-2023-4039.patch was also submitted for kirkstone and dunfell.
Should I attempt to cherry-pick this fix for those branches too?
Steve
On Fri, Sep 15, 2023 at 10:42 AM Martin Jansa wrote:
>
> * see:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111418
>
appstream has a dependency on it
- add a patch to fix a reproducibility and runtime issue with ptest
ptest completes without error
- add the recipe to ptest-packagelists.inc
Signed-off-by: Markus Volk
---
.../distro/include/ptest-packagelists.inc | 1 +
On Mon, Sep 18 2023 at 02:44:00 PM +02:00:00, Alexander Kanavin
wrote:
The criteria is written in the file where ptests are separated into
fast and slow.
Well documented. You just have to open your eyes ;)
Thanks. I'll send an update
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
The criteria is written in the file where ptests are separated into
fast and slow.
Alex
On Mon, 18 Sept 2023 at 14:39, Markus Volk wrote:
>
> On Mon, Sep 18 2023 at 01:40:25 PM +02:00:00, Markus Volk
> wrote:
>
> I did that already to check if the test is working at all. It took a few
>
assertTrue is a problematic call use in test cases since when it fails,
you just get an unhelpful "False is not True" message.
Replace some uses with assertIn/assertNotIn which will give more helpful results
and for the rest, add msg entries which given more helpful debugging.
For example, this
On Mon, Sep 18 2023 at 01:40:25 PM +02:00:00, Markus Volk
wrote:
I did that already to check if the test is working at all. It took a
few minutes. Didn't focus on that but I guess its been about 1-2
Minutes.
That is a fast one, I guess?
Tested this again with core-image-sato and runqemu
TUI mode needs terminfo at runtime, which is required to be
explicitly stated in the respective PACKAGECONFIG variable.
Without this change /etc/terminfo/ might be missing, which
leads to a runtime error when trying to use tui, e.g.:
(gdb) tui enable
Cannot enable the TUI: error opening terminal
On Sun, 2023-09-17 at 18:57 -0700, Robert Joslyn via
lists.openembedded.org wrote:
> NSS support was removed, so adjust PACKAGECONFIG options.
>
> The --enable-crypto-auth option was removed and split into separate
> options for basic-auth, bearer-auth, digest-auth, kerberos-auth,
>
On Mon, Sep 18 2023 at 01:33:56 PM +02:00:00, Alexander Kanavin
wrote:
You need to first check (with kvm) how long the tests are taking (and
that they pass, obviously), then add to one of the lists in
ptest-packagelists.inc.
I did that already to check if the test is working at all. It took a
You need to first check (with kvm) how long the tests are taking (and
that they pass, obviously), then add to one of the lists in
ptest-packagelists.inc.
Alex
On Mon, 18 Sept 2023 at 13:29, Markus Volk wrote:
>
> On Mon, Sep 18 2023 at 12:24:40 PM +01:00:00, Richard Purdie
> wrote:
>
> (and I
On Mon, Sep 18 2023 at 12:24:40 PM +01:00:00, Richard Purdie
wrote:
(and I suspect warnings from other targets will follow)
yes, I noticed that too. However, I couldn't decide where it had to be
entered and whether at all. That's why I left this question open
-=-=-=-=-=-=-=-=-=-=-=-
On Sun, 2023-09-17 at 20:28 +0200, Markus Volk wrote:
> appstream has a dependency on it
>
> - add a patch to fix a reproducibility and runtime issue with ptest
> ptest completes without error
>
> Signed-off-by: Markus Volk
> ---
> ...xb-selftest.c-hardcode-G_TEST_SRCDIR.patch | 35
On Mon, 18 Sept 2023 at 10:28, qi...@fujitsu.com wrote:
> Thanks for your reply.
> There are two ways to add markers. Which one is better?
> 1. add one marker for the hole test of tar (as your suggestion)
> 2. add markers(PASS, FAIL, SKIP) for every case
> sample:
> PASS: 1: tar version
> FAIL:
Hi， Alex
Thanks for your reply.
There are two ways to add markers. Which one is better?
1. add one marker for the hole test of tar (as your suggestion)
2. add markers(PASS, FAIL, SKIP) for every case
sample:
PASS: 1: tar version
FAIL: 5: TAR_OPTIONS with string arguments
SKIP: 11: --pax-option
Signed-off-by: Richard Purdie
---
.../lttng/{lttng-tools_2.13.10.bb => lttng-tools_2.13.11.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/lttng/{lttng-tools_2.13.10.bb =>
lttng-tools_2.13.11.bb} (99%)
diff --git
by removing the dependency, restarting the sshd service or starting it manually
will it generates keys?
recipes-core/openssh/files/sshd@.service
@@ -1,14 +1,12 @@
[Unit]
Description=OpenSSH Per-Connection Daemon
- Wants=sshdgenkeys.service
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
31 matches
Mail list logo
