Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: <olani@axis.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC PATCH 1/5] attr: Fix the ptest path to test-driver
Date: Wed, 13 Nov 2024 09:37:31 +0100	[thread overview]
Message-ID: <jwq4j4btdli.fsf@axis.com> (raw)
In-Reply-To: <621a6b4ca59c8035218d47c2194d19aecc922ff6.camel@linuxfoundation.org> (Richard Purdie's message of "Tue, 12 Nov 2024 09:35:39 +0000")


On Tue, Nov 12 2024, Richard Purdie wrote:

> On Mon, 2024-11-11 at 09:35 +0100, Ola x Nilsson via lists.openembedded.org wrote:
>> From: Ola x Nilsson <olani@axis.com>
>> 
>> Add a sed substitution for ${PTEST_PATH}/Makefile that transforms
>>  TEST_LOG_DRIVER = $(SHELL) $(top_srcdir)/build-aux/test-driver
>> to
>>  TEST_LOG_DRIVER = $(SHELL) $(top_builddir)/build-aux/test-driver
>> which is where the test-driver script can be found when installed.
>> 
>> There used to be an oe-core automake patch to do this, but it
>> broke non-ptest use of automake.
>> 
>> Relates to [YOCTO #15635]
>> ---
>>  meta/recipes-support/attr/attr.inc | 11 +++++++----
>>  1 file changed, 7 insertions(+), 4 deletions(-)
>
> Your patches are missing Signed-off-by lines. There is also a
> consistent ptest failure in acl:
>
> https://valkyrie.yoctoproject.org/#/builders/61/builds/366
> https://valkyrie.yoctoproject.org/#/builders/73/builds/366
> https://valkyrie.yoctoproject.org/#/builders/73/builds/367

I've found two recipes in meta-openembedded where ptests will fail if
the patch is removed.  Patches for those were just sent to openembedded-devel.

I don't understand the issue with acl.  The error in the log looks just
like if the updated sed substitution was not done.  I have not been able
to reproduce this, but I'll keep trying.

I've resent the series as v2 with Signed-off-by lines, but no other
changes.  


/Ola


  reply	other threads:[~2024-11-13 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11  8:35 [RFC PATCH 0/5] Remove automake patch that changes path to test-driver olani
2024-11-11  8:35 ` [RFC PATCH 1/5] attr: Fix the ptest " olani
2024-11-12  9:35   ` [OE-core] " Richard Purdie
2024-11-13  8:37     ` Ola x Nilsson [this message]
2024-11-11  8:35 ` [RFC PATCH 2/5] sed: " olani
2024-11-11  8:35 ` [RFC PATCH 3/5] parted: " olani
2024-11-11  8:35 ` [RFC PATCH 4/5] strace: " olani
2024-11-11  8:35 ` [RFC PATCH 5/5] automake: Remove patch that changes " olani
2024-11-11 10:52 ` [OE-core] [RFC PATCH 0/5] Remove automake " Alexander Kanavin

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=jwq4j4btdli.fsf@axis.com \
    --to=ola.x.nilsson@axis.com \
    --cc=olani@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox