1257195 - Check why NSS buildslave automation script occassionally reports FAILED for no reason

Status: RESOLVED WONTFIX

(NSS :: Test, defect, P5)

Description

[Kai Engert [:KaiE:]]

Occassionally, a slave on test.nss-crypto.org reports failed (red), although the log files don't show any failures.

(Note that the logfiles available from the web interface are filtered for brevity.)

E.g., for this recent build:
https://bot.nss-crypto.org:8011/builders/1-cpp11-linux-x64-DBG/builds/212

The full logfile ends with:


Tests summary:
--------------
Passed:             15300
Failed:             0
Failed with core:   0
Unknown status:     0

TB [2016-03-16 14:13:35] ######## details of detected failures (if any) ########
TB [2016-03-16 14:13:35] NSS - tests - 64 bits - DBG FAILED
TB [2016-03-16 14:13:35] ### result of run_cycle is 1
TB [2016-03-16 14:13:40] ### result of run_all is 1


There aren't any other occurrences of uppercase FAILED in the log file.

Comment 1

[Kai Engert [:KaiE:]]

In particular, this is the place that produces the result code:

https://hg.mozilla.org/projects/nss/file/tip/automation/buildbot-slave/build.sh#l210