On May 20, 2026 11:14 AM, Alexander Kanavin wrote: > Which are the conditions that trigger this? Presumably you're seeing this > locally, I do > wonder if there's a deeper issue here, and trying a different log file would > just obscure > it.
bootlog creation depends on SERIAL_CONSOLES count because serial_ports controls whether QemuRunner enables the extra serial socket path that feeds the unsuffixed log stream. testimage.bbclass sets: serial_ports = len(SERIAL_CONSOLES.split()) When serial_ports >= 2, QemuRunner creates threadsock and starts LoggingThread on that extra socket. Data from that path is written via self.log(data) (no extension) -> bootlog. When serial_ports < 2 , that extra socket path is not enabled, so the no-extension stream is absent. Logging still occurs through other paths ( self.log(..., ".2") , self.log(..., ".stdout") ), so bootlog.2 / bootlog.stdout can exist while bootlog does not. testimage_main() currently assumes bootlog always exists and unconditionally opens it on failure, which causes FileNotFoundError and masks the real test failure in <2 serial-console setups. On May 21, 2026 6:46 PM Ross Burton <Ross.Burton@...> wrote: > I think a better solution here would be to just list _all_ files that match > boot.log and > boot.log.*, so that the correct log is always shown. I’ll send a v2 that implements this approach: enumerate available bootlog variants (bootlog and bootlog.*) and print tail output from all matching files, instead of assuming a single fixed filename.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#241155): https://lists.openembedded.org/g/openembedded-core/message/241155 Mute This Topic: https://lists.openembedded.org/mt/119373684/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
