linux/poky.git/bitbake/lib/toaster/contrib/django-aggregate-if-master, branch master

bitbake: toastergui: fix error and warning counts for builds

2016-01-15T16:30:01+00:00

The error and warning counts displayed for builds were counts of the errors and warnings objects associated with a build. Because these values were being derived on the fly, it was not possible to sort by them. Previously, the 3rd party django-aggregate-if library was used to add aggregate fields to Build objects and should then have been used to populate the "all builds" and "project builds" tables. However, at some point the templates had changed so that the error and warning counts were coming from the properties on the Build model and not from these aggregates. This meant that it was not possible to sort by these fields. Django 1.8 supports conditional aggregates in annotation fields on querysets. This means we can remove django-aggregate-if, use the new Django 1.8 feature to derive errors_no and warnings_no fields as annotations, then use those annotation fields in the templates. This makes the "builds" tables sortable again. [YOCTO #8738] (Bitbake rev: 9be7c5c18b325f6ed40bc431ac408db242007eb1) Signed-off-by: Elliot Smith Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake: toaster: bring django-aggregate-if into the project

2015-06-26T08:27:32+00:00

We bring the django-aggregate-if module (with minor changes to import) into the project. (Bitbake rev: 4b92add34167304b45c66b9726cbc64bc0f74d9f) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: toaster: add django-aggregate-if

2015-06-26T08:27:32+00:00

Import library that provides conditional aggregates in Django. The tests are removed as they conflict with the Django startup. The sources are https://github.com/henriquebastos/django-aggregate-if Licence is MIT (Bitbake rev: 016b416fd0eaeab648a588053a2ee1f41bc02a84) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie