[Webhob] task types and outcomes

Damian, Alexandru alexandru.damian at intel.com
Fri May 31 05:48:10 PDT 2013


Thank you, Belen !

Recorded here, it this is part of our specification
https://wiki.yoctoproject.org/wiki/WebHob_general_architecture

Do we have a similar definition for build information, that I am not aware
of ?

Cheers,
Alex

On Fri, May 31, 2013 at 12:49 PM, Barros Pena, Belen <
belen.barros.pena at intel.com> wrote:

> I have managed to gather answers to most questions regarding task
> information for Web Hob (thanks Paul, Alex and Richard for you help!).
> I've updated bug 4275 with a new task information set
>
> https://bugzilla.yoctoproject.org/attachment.cgi?id=1232
>
> And a list of columns that will be available in the tasks table:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4275#c2
>
> Any questions or comments, let me know.
>
> Belen
>
> On 30/05/2013 15:28, "Richard Purdie" <richard.purdie at linuxfoundation.org>
> wrote:
>
> >On Thu, 2013-05-30 at 13:10 +0000, Dragomir, CalinX L wrote:
> >> I have a couple of questions regarding the tasks if you could help me
> >> understand better what's going on in a build operation.
> >>
> >> 1. From what I've read in the e-mails so far, it seems that there are
> >> three types of tasks: built, sstate and skipped. Can you tell me what
> >> each of them mean and how are they different ?
> >> 2. It also seems that there can be multiple results for each of them.
> >> Can you detail the meaning of each final state? (failed, missed,
> >> etc.) ?
> >> 3. How can I tell what type of task is the current executed task (if
> >> it is sstate or built or anything else) ?
> >
> >Let me explain what bitbake actually does. How this is presented in the
> >UI is a different question :)
> >
> >When you run "bitbake X", bitbake first goes through a "setscene" phase.
> >
> >This attempts to get the pre-built objects from the sstate cache. If
> >does this in reverse dependency order so it will try X, then the things
> >X depends on and so on.
> >
> >If it gets X, it would skip the dependencies in many cases.
> >
> >Bitbake then moves to the runqueue phase. If everything was obtained
> >from sstate, great, we do nothing. If we couldn't get anything, we'd
> >build from scratch. We also cover all the states in between.
> >
> >The tmp/stamps directory tells you the status of all the tasks. Each
> >task can have a stamp or a setscene version of the stamp.
> >
> >Hope that helps a bit!
> >
> >Cheers,
> >
> >Richard
> >
> >
> >
>
> ---------------------------------------------------------------------
> 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 part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20130531/d1ae7f5e/attachment.html>


More information about the toaster mailing list