Summary: | Odd case where one bundle failed to be signed | ||
---|---|---|---|
Product: | [WebTools] WTP Releng | Reporter: | David Williams <david_williams> |
Component: | releng | Assignee: | webtools.releng <webtools.releng-inbox> |
Status: | RESOLVED DUPLICATE | QA Contact: | David Williams <david_williams> |
Severity: | normal | ||
Priority: | P3 | Keywords: | info |
Version: | 3.10 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
David Williams
2011-05-11 12:08:23 EDT
The general issue of "unable to contact signing authority" is described and discussed in bug 321795, so will close as a dup of it, just to maintain cross-reference. As described there, there is no way for infrastructure to flag is as an error (jar signer just prints a message, doesn't use an exit code to flag the exception) so the only fix, as far as I know, is a post-build "releng test". This particular bug, though, is odd that is was exactly one bundle that 'failed to sign' ... guess signing authority was "unreachable" for only a few milliseconds?! *** This bug has been marked as a duplicate of bug 321795 *** |