From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Paul Eggleton <paul.eggleton@linux.intel.com>,
"Damian, Alexandru" <alexandru.damian@intel.com>,
"Dragomir, CalinX L" <calinx.l.dragomir@intel.com>,
"Zhang, Jessica" <jessica.zhang@intel.com>
Cc: "webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: [Webhob] task types and outcomes
Date: Tue, 28 May 2013 16:16:07 +0000 [thread overview]
Message-ID: <CDCA96D6.2ACE6%belen.barros.pena@intel.com> (raw)
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.
Built tasks can have 3 possible outcomes: previously built, completed and
failed.
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?
* Wouldn't a previously built task be an sstate task?
Sorry if this is a dumb question, but I am not sure if there is some
subtle difference I am missing, of if we are talking about different
'stages' of a single task's life cycle (to call it something).
Could anybody help me clarify this?
Thanks!!
Belén
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next reply other threads:[~2013-05-28 16:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 16:16 Barros Pena, Belen [this message]
2013-05-28 16:24 ` [Webhob] task types and outcomes Paul Eggleton
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=CDCA96D6.2ACE6%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=alexandru.damian@intel.com \
--cc=calinx.l.dragomir@intel.com \
--cc=jessica.zhang@intel.com \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--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.