From: Scott Garman <scott.a.garman@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: About autobuilder images
Date: Fri, 26 Nov 2010 19:52:04 -0800 [thread overview]
Message-ID: <4CF08064.1030604@intel.com> (raw)
Meant to cc: the list.
Scott
-------- Original Message --------
Subject: Re: [yocto] About autobuilder images
Date: Fri, 26 Nov 2010 20:48:35 -0700
From: Scott Garman <scott.a.garman@intel.com>
To: Tian, Kunwei <kunwei.tian@intel.com>
On 11/25/2010 01:55 AM, Tian, Kunwei wrote:
> Hi, Elizabeth I find the folder 20101123-1 and folder 20101124-1 are
> empty,which from http://autobuilder.pokylinux.org/nightly/. Do you
> know what is the matter? And also , I find folder 20101115-1 only
> have qemu images,but folder 20101115-2 is ok. What is the different
> between folder 20101115-1 and folder 20101115-2?
Most likely you're looking at output from a build that was canceled.
Previously, the output directories in the web area were only created at
the very end of the buildset, and the images copied over in one big
step. However, due to the length of time builds were taking and our need
to make the images available to QA as quickly as possible, images are
now copied over to the web area in several steps (generally as each main
machine arch is completed).
The -1 vs. -2 directory naming definitely indicates that the first build
was originally canceled and a second one was run.
To make this clearer, I'm thinking at the start of the build to touch a
file named BUILD_INCOMPLETE or somesuch, and then delete that at the
very end of the build, to clarify the state of the build. I can probably
add this early next week.
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
next reply other threads:[~2010-11-27 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 3:52 Scott Garman [this message]
2010-11-29 18:05 ` About autobuilder images Elizabeth Flanagan
-- strict thread matches above, loose matches on Subject: below --
2010-11-25 9:55 Tian, Kunwei
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=4CF08064.1030604@intel.com \
--to=scott.a.garman@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.