All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto <yocto@yoctoproject.org>
Cc: aaron.chun.yew.chan@intel.com
Subject: Release candidate build for Yocto Project 2.5 M3 rc1
Date: Wed, 21 Mar 2018 09:43:44 +0000	[thread overview]
Message-ID: <1521625424.25754.214.camel@linuxfoundation.org> (raw)

Hi,

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.

Any questions let me know.

Cheers,

Richard




                 reply	other threads:[~2018-03-21  9:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1521625424.25754.214.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=aaron.chun.yew.chan@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.