Re: Autobuilder pending failures

Naveen Saini

Hi Richard,

-----Original Message-----
From: swat@... <swat@...> On Behalf
Of Richard Purdie
Sent: Wednesday, December 23, 2020 8:44 PM
To: swat@...
Subject: [swat] Autobuilder pending failures

The autobuilder doesn't stop running over the holidays so I'm going to list the
failures I haven't been able to log/handle (and I'll probably reply to this to
add new ones if I spot them):

initramfs-boot reproducibility failure:

[Naveen] Cause of failure: device node permission bits are not set (/dev/console).
From the recipe do_install():
mknod -m 622 ${D}/dev/console c 5 1

From diff-html:

reproducibleA/tmp/deploy/deb/all/initramfs-boot_1.0-r2_all.deb vs

3 crw--w--w-···0·root·········(0)·root·········(0)····5,··1·1970-01-01·00:00:00.000000·./dev/console
3 crw-------···0·root·········(0)·root·········(0)····5,··1·1970-01-01·00:00:00.000000·./dev/console

Raised Bug#14162 []

qemuppc-alt ping timeout:
[Naveen] Ping test is failing only with core-image-sato, but passing with core-image-sato-sdk and core-image-full-cmdline. Not sure why it is happening. This issue is observed with master-next. Should I raise bug ?

intermittent arm ptest failures:
(the exact ones change a bit each run but we really need open bugs for each
one so that someone can ultimately investigate and fix them)
[Naveen] Bug raised.

qemumips64 shutdown backtrace:
[Naveen] Bug raised #14166 []

If anyone does have some time to file/update bugs or investigate any of the
above please feel free and reply to the email. If not, we'll get to things in
January unless I get bored!

master-next also have something toxic to oe-selftest in it which I've yet to
track down. I plan to keep -next running at a slower pace just to keep on top
of incoming patches as not everywhere is on holiday right now.



Join { to automatically receive all group messages.