[gnome-continuous-yocto/gnomeostree-3.28-rocko: 2549/8267] bitbake: toaster: Fix links to tasks with specific outcome
- From: Emmanuele Bassi <ebassi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-continuous-yocto/gnomeostree-3.28-rocko: 2549/8267] bitbake: toaster: Fix links to tasks with specific outcome
- Date: Sat, 16 Dec 2017 23:23:11 +0000 (UTC)
commit 67ce1ce3cbfa1977761ad668bdd548e7389211c3
Author: Belen Barros Pena <belen barros pena linux intel com>
Date: Sun Sep 18 19:33:13 2016 -0700
bitbake: toaster: Fix links to tasks with specific outcome
The build dashboard provides a count of tasks that were executed and not
executed, and of tasks that failed (if any). The number is a link to the
list of tasks.
Fix the links so that they filter the tasks table by the selected
criteria (executed, not executed or failed).
[YOCTO #9832]
(Bitbake rev: a75e70bbc9081f77f1e4aeeee8222b06112e4406)
Signed-off-by: Belen Barros Pena <belen barros pena linux intel com>
Signed-off-by: bavery <brian avery intel com>
Signed-off-by: Richard Purdie <richard purdie linuxfoundation org>
.../toastergui/templates/builddashboard.html | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/bitbake/lib/toaster/toastergui/templates/builddashboard.html
b/bitbake/lib/toaster/toastergui/templates/builddashboard.html
index 9e6e1c1..1c390cd 100644
--- a/bitbake/lib/toaster/toastergui/templates/builddashboard.html
+++ b/bitbake/lib/toaster/toastergui/templates/builddashboard.html
@@ -235,7 +235,7 @@
</a>
{% elif exectask.count > 1%}
- <a class="text-danger" href="{% url "tasks" build.id
%}?filter=outcome%3A4">{{exectask.count}}</a>
+ <a class="text-danger" href="{% url "tasks" build.id
%}?limit=25&page=1&orderby=order&filter=task_outcome:failed&default_orderby=order&filter_value=on&">{{exectask.count}}</a>
{% endif %}
</dd>
{% endif %}
@@ -244,12 +244,12 @@
Tasks executed
<span class="glyphicon glyphicon-question-sign get-help" title="'Executed' tasks are those
that need to be run in order to generate the task output"></span>
</dt>
- <dd><a href="{% url 'tasks' build.pk
%}?filter=task_executed%3A1&count=25&search=&page=1&orderby=order%3A%2B">{% query
build.task_build task_executed=1 order__gt=0 as exectask%}{{exectask.count}}</a></dd>
+ <dd><a href="{% url 'tasks' build.pk
%}?limit=25&page=1&orderby=order&filter=execution_outcome:executed&default_orderby=order&filter_value=on&">{%
query build.task_build task_executed=1 order__gt=0 as exectask%}{{exectask.count}}</a></dd>
<dt>
Tasks not executed
<span class="glyphicon glyphicon-question-sign get-help" title="'Not executed' tasks don't
need to run because their outcome is provided by another task"></span>
</dt>
- <dd><a href="{% url 'tasks' build.pk
%}?filter=task_executed%3A0&count=25&search=&page=1&orderby=order%3A%2B">{% query
build.task_build task_executed=0 order__gt=0 as noexectask%}{{noexectask.count}}</a></dd>
+ <dd><a href="{% url 'tasks' build.pk
%}?limit=25&page=1&orderby=order&filter=execution_outcome:not_executed&default_orderby=order&filter_value=on&">{%
query build.task_build task_executed=0 order__gt=0 as noexectask%}{{noexectask.count}}</a></dd>
<dt>
Reuse
<span class="glyphicon glyphicon-question-sign get-help" title="The percentage of 'not
executed' tasks over the total number of tasks, which is a measure of the efficiency of your build"></span>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]