Mercurial > treepkg
view recipes/gnupg/pkits.html @ 310:26c15a0f0e52
When stopping because of an error, do not raise the exception again as
it leads to confusing double tracebacks in the log. Instead, simply log
the reason for the stopping and stop in the same way a stop instruction
is handled.
author | Bernhard Herzog <bh@intevation.de> |
---|---|
date | Wed, 02 Dec 2009 14:46:37 +0000 |
parents | 27e78096a3fe |
children |
line wrap: on
line source
<html xmlns:py="http://genshi.edgewall.org/"> <head> <title>PKITS Log for GnuPG2 rev. ${pkits.revision}</title> <style type="text/css"> .statustable { background:#F4F4F4; } .statustablehead { background:#E0E0E0; } .statusheading { font-weight:bold; } .PASS { background:#C0FFC0; } .SKIP { background:#FFFFC0; } .FAIL { background:#FFC0C0; } .UNRESOLVED { background:#D0D0D0 } .unknown { background:#FFFFFF } tr { background:#FFFFFF; } td { padding:5px; } </style> </head> <body> <H1>PKITS Log for GnuPG2 rev. ${pkits.revision}</H1> <table class="statustable"> <tr> <th class="statustablehead">Test ID</th> <th class="statustablehead">Status</th> <th class="statustablehead">Details</th> </tr> <py:for each="line in pkits.lines"> <py:with vars="testid, status, details = line.split(None, 2)"> <tr class="${status in ['PASS', 'SKIP', 'FAIL', 'UNRESOLVED'] and status or 'unknown'}"> <td>${testid}</td> <td>${status}</td> <td>${details}</td> </tr> </py:with> </py:for> </table> </body> </html>