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 _______________________________________________ webhob mailing list [email protected] https://lists.yoctoproject.org/listinfo/webhob
