Invocation server: show actions with console output separately

Normally, actions are supposed to work silently, i.e., without writing
to stdout/stderr. So, if an action produces console output, it is
definitely worth looking at, even for cached actions. Therefore,
add a section after the failed actions showing those actions (if
not in the previous action). Also, always show duration (if known)
and if an action is cached (which can happen for the ones producing
console output).

1 files changed, 17 insertions, 0 deletions

diff --git a/doc/invocations-http-server/templates/invocation.html b/doc/invocations-http-server/templates/invocation.html
index 50d5690a..2ebebb86 100644
--- a/doc/invocations-http-server/templates/invocation.html
+++ b/doc/invocations-http-server/templates/invocation.html
@@ -38,6 +38,12 @@ Inocations {{invocation | e}}
         </ul>
       </li>
       {% endif %}
+      {% if action["duration"] %}
+      <li> duration: {{ action["duration"] | e  }}</li>
+      {% endif %}
+      {% if action["cached"] %}
+      <li> cached: {{ action["cached"] | e }}</li>
+      {% endif %}
       {% if action["exit_code"] != 0 %}
       <li> exit code: {{ action["exit_code"] }}</li>
       {% endif %}
@@ -187,6 +193,17 @@ Inocations {{invocation | e}}
 <i>(none)</i>
 {% endif %}
 
+<h3>Other actions with console output</h3>
+{% if output_actions %}
+<ul>
+  {% for action in output_actions %}
+  {{ show_action(action) }}
+  {% endfor %}
+</ul>
+{% else %}
+<i>(none)</i>
+{% endif %}
+
 
 <h3>Remaining non-cached actions</h3>
 {% if non_cached %}