From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Dragomir, CalinX L" <calinx.l.dragomir@intel.com>
Cc: "Zhang, Jessica" <jessica.zhang@intel.com>,
"webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: [Webhob] Django models
Date: Wed, 05 Jun 2013 18:14:44 +0100 [thread overview]
Message-ID: <5116417.al1Mo7JSpa@helios> (raw)
In-Reply-To: <27CEE5FF4D395E43B04459808802ADB7013EFFE0@IRSMSX106.ger.corp.intel.com>
Hi Calin,
On Wednesday 05 June 2013 11:23:57 Dragomir, CalinX L wrote:
> I've updated the Django models information based on this.
> The outcome is now limited only to these five options discussed.
> Please find my changes here:
> https://wiki.yoctoproject.org/wiki/Django_models
Some feedback on the models:
* I understand task_history is meant to capture where BitBake could have
accelerated the task using sstate but was unable to for some reason. Can we
have a choice field which indicates this directly (e.g. sstate_result - not
applicable, unavailable, failed, restored)?
* I agree we want to have a sequence number to allow us to easily show the
order tasks ran in within the UI where needed (is that task_number in the
current model? If so do we need the order field which is also listed?)
* I wonder if task_type should instead be an boolean value indicating if the
task executed or not; I can't think of any other value we'd want here that
isn't already covered by task_outcome.
* What is the "code" field?
* "py_sh" should probably be named "script_type" or similar
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-05 17:15 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
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 ` Paul Eggleton [this message]
2013-06-06 9:27 ` [Webhob] Django models 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=5116417.al1Mo7JSpa@helios \
--to=paul.eggleton@linux.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.