bitbake, oe-core and meta-yocto tags in sync? (was Re: GPIT LAVA Test Report - Job 123474: OEQA ALL PASSED (24/75) passed)

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Tue, Nov 11, 2025 at 10:35:08AM -0800, ledge-bot@linaro.org wrote:
> LAVA Test Report for Job 123474
> ==================================================
> 
> GitLab Pipeline Information:
>   Project: gpit
>   Branch: main
>   Pipeline: https://gitlab.com/Linaro/trustedsubstrate/gpit/-/pipelines/2152817594
>   bitbake: 2c6c40bdab8ebc6c04fe9992524add967fb4a053
>   bitbake git describe: yocto-5.2.1-149-g2c6c40bda
>   openembedded-core: e556df28f47e754b53e1f46c97dde2b19fd8fad1
>   openembedded-core git describe: uninative-5.0-152-ge556df28f4
>   meta-yocto: 66ea31cee15309af07afeee8dec8a6fe1d92d28e
>   meta-yocto git describe: 5.3_M3-3-g66ea31c

So this is our first build and test run with separate bitbake,
oe-core and meta-yocto built using kas to replace old poky repo master
branch which no longer builds. Setup details in
https://gitlab.com/Linaro/trustedsubstrate/gpit

The "git describe" output with tags is a bit confusing. Would it be
possible to use same version/milestone names there?

Currently it's a bit hard to tell if the trees are fully in sync and if
yocto-5.2.1, uninative-5.0 and 5.3_M3 are compatible with each other
or not. From pure tags it is not easy to see if trees used same
branches, for example.

> LAVA Job Information:
>   Job ID: 123474
>   Description: gpit-kv260
>   Device: laa-00077-kv260
>   State: Finished
>   URL: https://ledge.validation.linaro.org/scheduler/job/123474
> 
> OEQA Test Results Summary:
>   Total Tests: 75
>   Passed: 24
>   Failed: 0
>   Errors: 0
>   Skipped: 51

But at least all executed oeqa rutime tests on core-image-sato
with genericarm64 machine passed on AMD kv260 which is the same
result as with poky from one week ago before its retirement.

> Passed Tests:
>   - connman.ConnmanTest.test_connmand_help
>   - connman.ConnmanTest.test_connmand_running
>   - date.DateTest.test_date
>   - df.DfTest.test_df
>   - oe_syslog.SyslogTest.test_syslog_running
>   - oe_syslog.SyslogTestConfig.test_syslog_logger
>   - oe_syslog.SyslogTestConfig.test_syslog_restart
>   - opkg.OpkgRepoTest.test_opkg_install_from_repo
>   - pam.PamBasicTest.test_pam
>   - parselogs.ParseLogsTest.test_get_context
>   - parselogs.ParseLogsTest.test_parselogs
>   - ping.PingTest.test_ping
>   - python.PythonTest.test_python3
>   - scp.ScpTest.test_scp_file
>   - ssh.SSHTest.test_ssh
>   - systemd.SystemdBasicTests.test_systemd_basic
>   - systemd.SystemdBasicTests.test_systemd_failed
>   - systemd.SystemdBasicTests.test_systemd_list
>   - systemd.SystemdJournalTests.test_systemd_boot_time
>   - systemd.SystemdJournalTests.test_systemd_journal
>   - systemd.SystemdServiceTests.test_systemd_disable_enable
>   - systemd.SystemdServiceTests.test_systemd_status
>   - systemd.SystemdServiceTests.test_systemd_stop_start
>   - xorg.XorgTest.test_xorg_running

And we now list the passing tests in this report.
I think this is a useful detail to have.

Cheers,

-Mikko
 
> LAVA Test Suite Results:
>   BITBAKE_COMMIT_HASH: 2c6c40bdab8ebc6c04fe9992524add967fb4a053
>   BITBAKE_GIT_DESCRIBE: yocto-5.2.1-149-g2c6c40bda
>   METAYOCTO_COMMIT_HASH: 66ea31cee15309af07afeee8dec8a6fe1d92d28e
>   METAYOCTO_GIT_DESCRIBE: 5.3_M3-3-g66ea31c
>   OECORE_COMMIT_HASH: e556df28f47e754b53e1f46c97dde2b19fd8fad1
>   OECORE_GIT_DESCRIBE: uninative-5.0-152-ge556df28f4
> 
> This is an automated test report.