Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Yocto Project <yocto@lists.yoctoproject.org>
Cc: otavio@ossystems.com.br, yi.zhao@windriver.com,
	apoorv.sangal@intel.com, ee.peng.yeoh@intel.com,
	aaron.chun.yew.chan@intel.com,
	 richard.purdie@linuxfoundation.org, akuster808@gmail.com,
	 sjolley.yp.pm@gmail.com, sangeeta.jain@intel.com,
	Steve Sakoman <steve@sakoman.com>
Subject: QA notification for completed autobuilder build (yocto-3.1.3.rc1)
Date: Fri, 25 Sep 2020 15:36:10 +0100	[thread overview]
Message-ID: <032da6fc700a4018bc7e8d86fd188ad6b40fce36.camel@linuxfoundation.org> (raw)
In-Reply-To: 20200924111808.4B9ED1A00A2@debian8-ty-1.yocto.io

[the original email bounced for some reason, resending to the list]

A build flagged for QA (yocto-3.1.3.rc1) was completed on the
autobuilder and is available at:


    https://autobuilder.yocto.io/pub/releases/yocto-3.1.3.rc1


Build hash information: 

bitbake: 18e1957337fd9f06bc673d28dd4f8277321d07bc
meta-arm: c7a1a5f9fd415e3ae1078c2a1d6af9c25e9e6498
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: d7134e86574172784f90117c03a012e0048d8bcb
meta-kernel: cb7f0dc5bb1ea0998c8d4fcb486148d4cab575f4
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
oecore: b39bda4cc62db12c0edfbe489d5a7f5988ede6a9
poky: 012ad10a89a889c21e67c27dc37d22520212548f



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@linuxfoundation.org



       reply	other threads:[~2020-09-25 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200924111808.4B9ED1A00A2@debian8-ty-1.yocto.io>
2020-09-25 14:36 ` Richard Purdie [this message]
2020-09-28 14:52   ` QA notification for completed autobuilder build (yocto-3.1.3.rc1) Sangeeta Jain
2020-10-01  7:17   ` Sangeeta Jain

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=032da6fc700a4018bc7e8d86fd188ad6b40fce36.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=aaron.chun.yew.chan@intel.com \
    --cc=akuster808@gmail.com \
    --cc=apoorv.sangal@intel.com \
    --cc=ee.peng.yeoh@intel.com \
    --cc=otavio@ossystems.com.br \
    --cc=sangeeta.jain@intel.com \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=steve@sakoman.com \
    --cc=yi.zhao@windriver.com \
    --cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox