From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Reyna, David" <david.reyna@windriver.com>,
"toaster@lists.yoctoproject.org"
<toaster@lists.yoctoproject.org>
Cc: Randy MacLeod <randy.macleod@windriver.com>
Subject: Toaster tweaks
Date: Sun, 30 Aug 2026 08:01:47 +0100 [thread overview]
Message-ID: <48aff66859abb9e30d2f61e51ff449ece5e8db4e.camel@linuxfoundation.org> (raw)
Hi All,
We've noticed toaster was failing more frequently on the autobuilder. I
did a little digging as I wanted to understand why.
Problem 1:
I broke one of the scripts, fixed here:
https://git.openembedded.org/bitbake/commit/?id=75c85c54d9bcc5b732459bef183bab79db00c843
Problem 2:
The layer index has some data the code doesn't like after recent index
changes. I hacked around it:
https://git.openembedded.org/bitbake/commit/?id=74d8b3ad3fe2ce43860819fbb934bbc70cc14b56
We really could do with a better fix for that but this unblocks tests.
Problem 3:
Flaky tests, at least locally:
https://git.openembedded.org/bitbake/commit/?id=3e63c225d8e107526c4b4c8ccb5a85720c665ca1
There are probably more places we need this change. I've also realised
this doesn't fix all the failures I can see locally as the viewport may
end up in the wrong place. I have further local changes which I might
try and clean up next week. We need to continually improve this kind of
issue.
Problem 4:
Our version of django is out of support. I do have a patch from
"django-upgrade" in testing which I could send out for others to
test/review. I'm not 100% convinced by it yet.
For those new to toaster, you can run the tests locally with:
pip install -r ../layers/bitbake/toaster-requirements.txt -r ../layers/bitbake/lib/toaster/tests/toaster-tests-requirements.txt
mkdir toaster_logs
pytest -c ../layers/bitbake/lib/toaster/pytest.ini ../layers/bitbake/lib/toaster/tests/
or an individual test file as:
pytest -c ../layers/bitbake/lib/toaster/pytest.ini ../layers/bitbake/lib/toaster/tests/browser/test_layerdetails_page.py
Cheers,
Richard
next reply other threads:[~2026-08-30 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 7:01 Richard Purdie [this message]
2026-08-31 7:11 ` Toaster tweaks Reyna, David
2026-09-01 23:21 ` 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=48aff66859abb9e30d2f61e51ff449ece5e8db4e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=david.reyna@windriver.com \
--cc=randy.macleod@windriver.com \
--cc=toaster@lists.yoctoproject.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 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.