Hello,
We are pleased to announce the Yocto Project 3.3.3 (hardknott-25.0.3) Release
is now available for download.
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.3/poky-hardknott-25.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.3/poky-hardknott-25.0.3.tar.bz2
A gpg
Recent upstream kernel changes have made the mmc probing order unpredictable.
Therefore, boards with both an emmc and sdmmc interface aren't guaranteed to
boot with a hard-coded root device selected.
For example, on the rock64, with linux-yocto 5.10.y, using the uSD card (i.e.
the sdmmc
Hello,
We are pleased to announce the Yocto Project 3.3.3 (hardknott-25.0.3) Release
is now available for download.
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.3/poky-hardknott-25.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.3/poky-hardknott-25.0.3.tar.bz2
A gpg
On 2021-09-16 11:33 a.m., Trevor Gamblin wrote:
On 2021-09-16 11:33 a.m., Trevor Gamblin wrote:
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage
*Attendees:* Alex, Diane, Jon, Joshua, Michael, Richard, Ross, Saul,
Stephen, Steve, Tim, Trevor
*ARs:*
- Trevor to move old AB defects
On Wed, Sep 15, 2021 at 5:10 PM Trevor Woerner wrote:
> The rock64 has an ARM Mali 450 MP2 GPU, therefore enable mesa's lima for
> accelerated, open-source graphics.
>
> Signed-off-by: Trevor Woerner
> ---
> recipes-graphics/mesa/mesa_%.bbappend | 1 +
> 1 file changed, 1 insertion(+)
>
Currently, ptest-runner simply kills the offending test without further ado,
which is not at all helpful when trying to figure out why it happens
(especially if such hangs are intermittent and rare). There's now a script
that gets executed before killing the test, so ideas on what to have in it
if poll()'s timeout expires that means the test did not
produce any output, which is exactly what we need to catch.
So there's no need to set up separate timeouts with signals
and alarms, and this greatly simplifies more sophisticated
processing of hanging tests (such as collecting overall system
I also took the opportunity to correct a weird API that
returns a result (or not), depending on some internal condition.
Signed-off-by: Alexander Kanavin
---
tests/utils.c | 35 ++-
1 file changed, 18 insertions(+), 17 deletions(-)
diff --git a/tests/utils.c
There are additional logs there (such as task log or qemu
console output), which can be useful for debugging test failures.
[YOCTO #14518]
Signed-off-by: Alexander Kanavin
---
scripts/collect-results | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git
