Typically in core-image-sato-1.0-r0 do_testsdkext Recent examples: https://errors.yoctoproject.org/Errors/Details/415724/ https://errors.yoctoproject.org/Errors/Details/414804/ https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/1945 Rerunning the build has always succeeded for me
This looks like some kind of issue related to source date epoch in the eSDK :/
Another instance today, this time in core-image-minimal-1.0-r0 do_testsdkext: core-image-minimal: https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/2034
Haven't seen these in a while, but leaving open
Another occurrence on dunfell (ubuntu1804-ty-1, core-image-minimal-1.0-r0 do_testsdkext) https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/2311
https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/2482
I got this while building gatesgarth today. https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/3073
Another occurrence on dunfell (fedora32-ty-1, core-image-minimal-1.0-r0 do_testsdkext): https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/3337
There are some source data epoch changes that were made in master/honister that we should consider backporting to dunfell.
SDE changes backported from master, so closing.
Started happening again on dunfell this week: qemuppc debian9-ty-2 https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/4749 qemuarm64 ubuntu1804-ty-3 https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/4777
https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/5251/steps/17/logs/stdio qemumips64 debian9-ty-2
RP suspects that this could be related to source-data-epoch changes which are too invasive to backport to dunfell. Wait a few more months to see if it happens more frequently.
As per previous comment.