From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH] lib/bb/tests: use bb.build.listtasks() instead of __BBTASKS
Date: Wed, 04 Dec 2024 18:29:28 +0100 [thread overview]
Message-ID: <D633ECVEQJPV.RW45QS9AIPTJ@bootlin.com> (raw)
In-Reply-To: <20241204101911.1218039-1-ross.burton@arm.com>
On Wed Dec 4, 2024 at 11:19 AM CET, Ross Burton via lists.openembedded.org wrote:
> Use the new listtasks() function (introduced in 185c4b) to avoid
> accessing a private variable.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
Hi Ross,
I believe some oe-selftest will need update after this modification. I
have the following error on the autobuilder:
FAIL: test_parse_addtask_deltask (bb.tests.parse.ParseTest.test_parse_addtask_deltask)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-ubuntu/build/bitbake/lib/bb/tests/parse.py", line 204, in test_parse_addtask_deltask
self.assertEqual(['do_fetch2', 'do_patch2', 'do_myplaintask', 'do_mytask', 'do_mytask2', 'do_mytask5'], bb.build.listtasks(d))
AssertionError: ['do_fetch2', 'do_patch2', 'do_myplaintas[39 chars]sk5'] != ('do_fetch2', 'do_patch2', 'do_myplaintas[39 chars]sk5')
https://valkyrie.yoctoproject.org/#/builders/48/builds/502/steps/11/logs/stdio
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-12-04 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 10:19 [PATCH] lib/bb/tests: use bb.build.listtasks() instead of __BBTASKS Ross Burton
2024-12-04 17:29 ` Mathieu Dubois-Briand [this message]
2024-12-04 17:46 ` [bitbake-devel] " Ross Burton
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=D633ECVEQJPV.RW45QS9AIPTJ@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ross.burton@arm.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.