From: Petr Vorel <petr.vorel@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org,
Yi Zhao <yi.zhao@eng.windriver.com>,
Khem Raj <raj.khem@gmail.com>,
Hui Min Mina Chou <minachou@andestech.com>
Subject: Re: [PATCH 1/1] ltp: upgrade 20250530 -> 20250930
Date: Fri, 17 Oct 2025 18:43:32 +0200 [thread overview]
Message-ID: <20251017164332.GA355538@pevik> (raw)
In-Reply-To: <59f5af6c290efef806b73ba905cbfc412c290109.camel@linuxfoundation.org>
Hi Richard,
> On Mon, 2025-10-13 at 20:59 +0200, Petr Vorel wrote:
> > Hi Richard, all,
> > [ I accidentally deleted mail thread. Unfortunately I don't see Message-id in
> > web UI [1] therefore I cannot set In-Reply-To:. Due this also any reply to other
> > LTP developers about runltp vs. kirk would not be in the thread ]
> > > > $ . oe-init-build-env
> > > > .../build $ bitbake ltp
> > > > ERROR: Error importing OE modules: module 'bb.parse' has no attribute
> > > > 'vardepsexclude'
> > > > ERROR: Unable to parse
> > > > /home/pvorel/install/src/openembedded/bitbake/lib/bb/parse/ast.py
> > > > Traceback (most recent call last):
> > > > ďż˝ File
> > > > ďż˝ "/home/pvorel/install/src/openembedded/bitbake/lib/bb/parse/ast.py",
> > > > ďż˝ line 372, in eval
> > > > ����� layerid, fragment_name = f.split('/', 1)
> > > > ����� ^^^^^^^^^^^^^^^^^^^^^^
> > > > ďż˝ ValueError: not enough values to unpack (expected 2, got 1)
> > > > FYI I also plan to get rid of some patches posted.
> > > Are you setting OE_FRAGMENTS to something in a config file? It
> > > shouldn't traceback like this so that is a bug but something is
> > > triggering it...
> > No, simple clone and the 2 commands above. I'll later try it again on fresh
> > git clone.
> If you could share the repo/branch you cloned (poky?) I'd appreciate it
> as I did try and reproduce that and couldn't. I will write some patches
> to improve the code/error regardless as that much is clear from the
> failure. It really shouldn't fail like that, it is embarrassing :/.
Master branch from my fork [1] do:
... $ . oe-init-build-env
./build $ bitbake ltp
ERROR: Error importing OE modules: module 'bb.parse' has no attribute 'vardepsexclude'
ERROR: Unable to parse /home/pvorel/install/src/openembedded/bitbake/lib/bb/parse/ast.py
Traceback (most recent call last):
File "/home/pvorel/install/src/openembedded/bitbake/lib/bb/parse/ast.py", line 372, in eval
layerid, fragment_name = f.split('/', 1)
^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)
Kind regards,
Petr
[1] https://github.com/pevik/openembedded-core
next prev parent reply other threads:[~2025-10-17 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 18:59 [PATCH 1/1] ltp: upgrade 20250530 -> 20250930 Petr Vorel
2025-10-14 11:09 ` Richard Purdie
2025-10-17 16:43 ` Petr Vorel [this message]
2025-10-17 18:18 ` [OE-core] " Alexander Kanavin
2025-10-18 10:05 ` Richard Purdie
2025-10-18 19:14 ` Petr Vorel
2025-10-20 11:25 ` Alexander Kanavin
[not found] ` <18702F64E374DBD3.535@lists.openembedded.org>
2025-10-21 17:52 ` Alexander Kanavin
2025-10-17 17:05 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2025-10-12 20:08 Petr Vorel
2025-10-12 22:15 ` Richard Purdie
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=20251017164332.GA355538@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=yi.zhao@eng.windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox