We had this error once on the autobuilder: ==================================================================================================== Importing test results repo data (1774397250.4) ==================================================================================================== INFO: Running git clone git@push.yoctoproject.org:yocto-testresults /tmp/sendqaemail.49purf0e --depth 1 --branch master Cloning into '/tmp/sendqaemail.49purf0e'... fatal: Needed a single revision Already on 'master' Your branch is up to date with 'origin/master'. Switched to branch 'master-next'
a-full fedora40-vk-1 master-next completed at 2026-03-25 00:28:18+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3506/steps/37/logs/stdio
From the logs: timeout 1200 secs ... There were lots of failures in that build. The configuration was broken and the build was very bad... Re-open if seen again.
This one looks similar. I now the ticket is closed, just logging if case we ever re-open. a-full ubuntu2510-vk-1 master&master-next completed at 2026-06-04 19:45:57+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3926/steps/37/logs/stdio
a-full rocky8-vk-1 master-next&master completed at 2026-08-01 02:25:06+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4353/steps/40/logs/stdio
Looking at that last build (https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4353). Build properties shows commit_oecore is "7e5354150173a585c33a833b9d6b11a1112ddbb9". In "Prepare shared repositories" I see for OE-core: HEAD is now at 0bb90e0c2e python3-websockets: upgrade 16.1.1 -> 17.0 Then in "Send QA Email" we run: resulttool store --revision 0bb90e0c2e2e3f9e6432300de66668feca93e75e ... As it gets the revision by looking at the HEAD commit in repos/oecore. Resulttool prints: INFO: Reading files from /srv/autobuilder/valkyrie.yocto.io/pub/non-release/20260731-126/testresults INFO: Found 1 revisions to store INFO: skipping 7e5354150173a585c33a833b9d6b11a1112ddbb9 as non-matching It's been told to store results for commit 0bb90e0c2e2e3f9e6432300de66668feca93e75e (from repos/oecore HEAD), but the results we generated are for commit 7e5354150173a585c33a833b9d6b11a1112ddbb9 (from layerindex.json?), so it doesn't store anything. Then "Processing regression report" fails as there are no stored results for the expected commit 7e5354150173a585c33a833b9d6b11a1112ddbb9. Perhaps master-next was pushed between when layerinfo.json was created on the controller and when "Prepare shared repositories" pulled OE-core on the worker.
Tag oecore/autobuilder.yoctoproject.org/valkyrie/a-full-4353 in https://git.openembedded.org/openembedded-core points at commit 0bb90e0c2e2e3f9e6432300de66668feca93e75e, not at the commit stored in the build properties for that build. Committer date of "2026-07-31 23:16:43 +0100" is just before the build start time of 2026-07-31T23:17:55+01:00. So I think this is a race between master-next being pushed and the build starting.
Bugzilla needs to let you edit comments... The link in my last comment should have been https://git.yoctoproject.org/poky-ci-archive.
a-full debian11-vk-1 master&master-next completed at 2026-08-06 02:20:46+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4399/steps/42/logs/stdio
Should be resolved by https://git.yoctoproject.org/yocto-autobuilder-helper/commit/?id=69ac985a0ebac9c17ee8e0353eb9369eca8cedb1 We also merged https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=861949062045c7c5198e885f99df0176679c9f30 which should help.
a-full debian13-vk-2 master&master-next completed at 2026-08-20 15:14:18+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4527/steps/40/logs/stdio
a-full ubuntu2504-vk-1 master-next&master completed at 2026-09-05 15:04:16+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4672/steps/40/logs/stdio
a-full fedora44-vk-3 master-next&master completed at 2026-09-29 15:04:44+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4828/steps/40/logs/stdio