NSS BuildBot Status

This page lists known issues related to the NSPR/NSS/JSS continuous integration builds found at http://test.nss-crypto.org

Hints

Most output shown in the buildbot log has been filtered, to suppress the vast amount of e.g. polling status information produced by the test tools.
At the end of the logfile, all FAILED results are printed with 50 lines of preceeeding context.

pkits.sh ERROR: Valid DSA Parameter Inheritance Test5 failed 5

occassionaly a build is red for no apparent reason, such as that final section of the logfile not reporting any matches for the string FAILED (besides the overall failure status). One possible reason is, occassionally, the "output directory rotation" is failing. As a result, directory tests_results/security is reused, and the output of a second build cycle is written into that directory (with hostname.2). This breaks the assumptions of the test scripts. This needs investigation how to ensure that directory rotation works reliably, or at least gets detected and reported.
Android: Building happens on a Linux computer and testing happens on an Android tablet. You might occassionally see the build to succeed, and the test failing, complaining about missing files. Most likely the Android tablet is offline. This can happen is the SSH daemon goes offline, or if the Android tablet looses its wifi connection. If this happens, the tablet's wifi and SSH daemon need to be manually checked/restarted.
we occassionally see test failures because the OCSP server cannot be reached from a build slave