Poky Project Discussions
 help / color / mirror / Atom feed
From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"poky@yoctoproject.org" <poky@yoctoproject.org>,
	"Wold, Saul" <saul.wold@intel.com>
Subject: Re: autobuilders in flux today.
Date: Thu, 17 Feb 2011 22:56:28 -0800	[thread overview]
Message-ID: <4D5E181C.5050208@intel.com> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB68637101D4A@shsmsx502.ccr.corp.intel.com>

Yes, there was some issues with the autobuilder due to some old processes. A quick reset of the autobuilder service this
afternoon and the current build is mostly green with the exception of one sanity test failure.

-b

On 02/17/2011 09:11 PM, Cui, Dexuan wrote:
> Hi Beth,
> Looks autobuilder is still unstable? 
> I found the following issues.
> Actually due to the 3rd failure(./poky-init-build-env: No such file or directory), almost all the builds failed...
> Could you please have a look?
> 
> Copying RPM feed output failed: Error: tmp/deploy/rpm does not exist, cannot copy!
> http://autobuilder.pokylinux.org:8010/builders/nightly-internal/builds/54/steps/shell_21/logs/stdio
> 
> 
> Generating Poky release tarball failed: fatal: Not a git repository (or any of the parent directories): .git
> http://autobuilder.pokylinux.org:8010/builders/nightly-internal/builds/54/steps/shell_19/logs/stdio
> 
> Building qemux86-64 meta-toolchain-sdk failed:
> /home/pokybuild/poky-autobuilder/scripts/poky-autobuild: line 35: ./poky-init-build-env: No such file or directory
> /home/pokybuild/poky-autobuilder/scripts/poky-autobuild: line 80: bitbake: command not found
> http://autobuilder.pokylinux.org:8010/builders/nightly-internal/builds/54/steps/shell_17/logs/stdio
> 
> 
> Thanks,
> -- Dexuan
> 
> -----Original Message-----
> From: poky-bounces@yoctoproject.org [mailto:poky-bounces@yoctoproject.org] On Behalf Of Elizabeth Flanagan
> Sent: 2011年2月17日 3:20
> To: yocto@yoctoproject.org; poky@yoctoproject.org
> Subject: [poky] autobuilders in flux today.
> 
> I came in this morning to 140 zombies and a build that was choking on builder2. I'm rebooting the server right now. Just
> an FYI, this is a relatively recent development (last night there were 17 zombies). Not sure what is going on but I'll
> keep everyone informed.
> 
> All that said, the autobuilders will be in flux today while I bring builder3 online. Please don't kick off anything vital.
> 
> Thanks
> 
> 
> ------------------
> Elizabeth Flanagan
> Yocto Project
> Release Engineer
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky

-- 
------------------
Elizabeth Flanagan
Yocto Project
Release Engineer


  reply	other threads:[~2011-02-18  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 19:19 autobuilders in flux today Elizabeth Flanagan
2011-02-18  5:11 ` Cui, Dexuan
2011-02-18  6:56   ` Elizabeth Flanagan [this message]
2011-02-21  6:38     ` Cui, Dexuan

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=4D5E181C.5050208@intel.com \
    --to=elizabeth.flanagan@intel.com \
    --cc=dexuan.cui@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=saul.wold@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox