12621 2018-03-22 20:05:41 +0000 [2.5 M3 rc1] nightly-qa-extras: Autobuilder2 failures with syslogd when systemd upgraded 2018-03-23 06:12:20 +0000 1 1 10 QA/Testing Build Testing general 2.5 x86 Multiple RESOLVED DUPLICATE 12618 https://autobuilder.yoctoproject.org/new/#/console Undecided normal --- 1 aaron.chun.yew.chan richard.purdie aaron.chun.yew.chan apoorv.sangal bluelightning ee.peng.yeoh robin.l.jordan ross.burton stephano aaron.chun.yew.chan --- Regression (Found by QA test) Don't know oldest_to_newest 79949 0 aaron.chun.yew.chan 2018-03-22 20:05:41 +0000 > We have a build ready for QA for the Yocto Project release 2.5 M3 rc1. > This build is slightly different in that it has been run on the new > autobuilder codebase. We don't have automated release emails yet so > I'm writing this manually. The release is available at: > > http://autobuilder.yoctoproject.org/pub/yocto-2.5_M3.rc1/ > > The build results can be seen at: > > https://autobuilder.yoctoproject.org/new/#/console > > As you can see, there was one failure in nightly-qa-extras to do with > syslogd under systemd images. Right now I think we note this for the > M3 release and fix during M4, it was caused by the systemd upgrade > which was added late on. We will need a bug for this. > > For comparison, I also built this release on the current yocto.io > infrastructure. I have an additional request for QA to compare the > list of artefacts generated from the new codebase with the artefacts > from the old codebase. Those are available here: > > https://autobuilder.yocto.io/pub/releases/yocto-2.5_M3.rc1/ > (from https://autobuilder.yocto.io/builders/nightly/builds/965 which > had the same qa-extras failure). > > I did already notice we're missing the top level tarballs , which is > odd since I know we do generate them. This is something we'll need to > investigate but I wouldn't block M3 on this. For start we file this bug to track the fix needed to be in 2.5 M4 79958 1 ross.burton 2018-03-23 06:12:20 +0000 The syslog problem is already tracked (and a patch is out). *** This bug has been marked as a duplicate of bug 12618 ***