From: Petr Vorel <petr.vorel@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org,
Khem Raj <raj.khem@gmail.com>,
Tim Orling <tim.orling@konsulko.com>,
Hui Min Mina Chou <minachou@andestech.com>
Subject: Re: [PATCH 1/1] ltp: Update to 20250130
Date: Sun, 2 Feb 2025 13:22:49 +0100 [thread overview]
Message-ID: <20250202122249.GA1150099@pevik> (raw)
In-Reply-To: <166c73cfa10449a1163cefae2879ca881f3b42f9.camel@linuxfoundation.org>
Hi Richard,
...
> I ran it through our automated testing and whilst the main tests ran
> ok, it failed on musl:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/932/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/948/steps/11/logs/stdio
Thank you for running the tests for me. Although we have musl (via Alpine) in
LTP CI, this error slipped in:
| CC testcases/kernel/syscalls/listen/listen01
| In file included from listmount01.c:22:
| listmount.h: In function 'listmount':
| listmount.h:18:16: error: variable 'req' has initializer but incomplete type
| 18 | struct mnt_id_req req = {
| | ^~~~~~~~~~
| listmount.h:19:18: error: 'struct mnt_id_req' has no member named 'size'
| 19 | .size = MNT_ID_REQ_SIZE_VER0,
| | ^~~~
Fortunately fix looks quite obvious (missing autotools guard).
I'll send Cc to LTP + v2 for yocto. I'll try to force myself to run the yocto
build myself to not bother you with testing for me.
Kind regards,
Petr
> Cheers,
> Richard
prev parent reply other threads:[~2025-02-02 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 22:54 [PATCH 1/1] ltp: Update to 20250130 Petr Vorel
2025-02-02 6:33 ` Richard Purdie
2025-02-02 12:22 ` Petr Vorel [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=20250202122249.GA1150099@pevik \
--to=petr.vorel@gmail.com \
--cc=minachou@andestech.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=tim.orling@konsulko.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.