From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "Dragomir, CalinX L" <calinx.l.dragomir@intel.com>,
"Zhang, Jessica" <jessica.zhang@intel.com>,
"webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: Re: [Webhob] task types and outcomes
Date: Tue, 28 May 2013 17:24:51 +0100 [thread overview]
Message-ID: <31133430.WWGx2hZGqK@helios> (raw)
In-Reply-To: <CDCA96D6.2ACE6%belen.barros.pena@intel.com>
On Tuesday 28 May 2013 16:16:07 Barros Pena, Belen wrote:
> I am looking into the BitBake task-related information we'll display in
> Web Hob. Looking back to the agency work, it seems we identified 2 types
> of tasks: sstate tasks and built tasks.
>
> Sstate tasks can have 3 possible outcomes: missed, completed and failed.
Correct (although I wonder if there is a further distinction between missed
completely, and missed due to some change i.e. one or more sstate packages
exist for the task but the signatures are different).
> Built tasks can have 3 possible outcomes: previously built, completed and
> failed.
Correct.
> Looking at this now, I am not sure I understand the difference between a
> missed sstate task and a built task, and between a previously built task
> and an sstate task:
>
> * Wouldn't a missed sstate task become a built task?
Yes.
> * Wouldn't a previously built task be an sstate task?
If the definition of "previously built" is "previously built within the same
build directory and not subsequently cleaned", then because there is a stamp
present for the task, it doesn't even need to look at sstate for the task.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-28 16:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 16:16 [Webhob] task types and outcomes Barros Pena, Belen
2013-05-28 16:24 ` Paul Eggleton [this message]
2013-05-28 17:17 ` Barros Pena, Belen
2013-05-29 15:57 ` Paul Eggleton
2013-05-29 21:39 ` Richard Purdie
2013-05-30 10:57 ` Barros Pena, Belen
2013-05-30 13:10 ` Dragomir, CalinX L
2013-05-30 13:51 ` Barros Pena, Belen
2013-05-30 14:28 ` Richard Purdie
2013-05-31 11:49 ` Barros Pena, Belen
2013-05-31 12:48 ` Damian, Alexandru
2013-05-31 13:18 ` Barros Pena, Belen
2013-05-30 14:21 ` Richard Purdie
2013-05-31 13:50 ` Barros Pena, Belen
2013-05-31 13:53 ` Otavio Salvador
2013-05-31 14:02 ` Paul Eggleton
2013-05-31 14:04 ` Dragomir, CalinX L
2013-06-03 12:32 ` Barros Pena, Belen
2013-06-05 10:40 ` Barros Pena, Belen
2013-06-05 11:23 ` Dragomir, CalinX L
2013-06-05 17:14 ` [Webhob] Django models Paul Eggleton
2013-06-06 9:27 ` Calin Dragomir
2013-06-06 11:06 ` Barros Pena, Belen
2013-06-06 12:54 ` Paul Eggleton
2013-06-07 11:04 ` Barros Pena, Belen
2013-06-07 11:52 ` [Webhob] Django models wiki updates Calin Dragomir
2013-06-12 11:03 ` Damian, Alexandru
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=31133430.WWGx2hZGqK@helios \
--to=paul.eggleton@linux.intel.com \
--cc=belen.barros.pena@intel.com \
--cc=calinx.l.dragomir@intel.com \
--cc=jessica.zhang@intel.com \
--cc=webhob@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.