On Thu, 2020-09-24 at 08:33 +0100, Richard Purdie via lists.yoctoproject.org wrote: > On Thu, 2020-09-24 at 03:22 +0000, Pokybuild User wrote: > > A build flagged for QA (yocto-3.2_M3.rc2) was completed on the > > autobuilder and is available at: > > > > > > https://autobuilder.yocto.io/pub/releases/yocto-3.2_M3.rc2 > > > > > > Build hash information: > > > > bitbake: 27b53186fa67d281d29b2f8e15bcff8dc2557b8a > > meta-arm: c7a1a5f9fd415e3ae1078c2a1d6af9c25e9e6498 > > meta-gplv2: a8da8eb127a56561bf633ab53bec57fb5dbba537 > > meta-intel: 254e3a79b3a37045f829848e0a5e04801bec1439 > > meta-kernel: cb7f0dc5bb1ea0998c8d4fcb486148d4cab575f4 > > meta-mingw: f1e1d5a803a48ed70f2b0eaf0ef15ade70479fce > > oecore: e68df923e1bf9e82662ee2619ac9e2f239e8f7be > > poky: 0a243cd21263f498b6eca7c0b168e655dd823e22 > > > > > > > > This is an automated message from the Yocto Project Autobuilder > > Git: git://git.yoctoproject.org/yocto-autobuilder2 > > Email: richard.pur...@linuxfoundation.org > > There were two failures in this build. One was a single selftest > failure which I'll look into. The other was a qemumips altcfg image > loss of networking. I know Saul is working on better debug for that > and we have open bugs for it.
Much to my surprise, I figured out the issue and there is a patch for the selftest failure on the bitbake list. It won't stop the release or QA. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50809): https://lists.yoctoproject.org/g/yocto/message/50809 Mute This Topic: https://lists.yoctoproject.org/mt/77050636/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
