Closed
Bug 1292611
Opened 8 years ago
Closed 8 years ago
buildbot: log entry with SSL_ERROR_HANDSHAKE_FAILURE_ALERT incorrectly leads to status "failed build"
Categories
(NSS :: Test, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
3.27
People
(Reporter: KaiE, Assigned: KaiE)
Details
Attachments
(1 file)
654 bytes,
patch
|
ttaubert
:
review+
|
Details | Diff | Splinter Review |
automation/buildbot-slave/build.sh uses grep -B50 FAIL ${OUTPUTFILE} to dump any fragments around failures, and it uses the grep result (lines found) to decide if there were failures. This worked in the past, but nowadays the log mentions error code SSL_ERROR_HANDSHAKE_FAILURE_ALERT, which apparently is expected, and doesn't mean a failure. It matches the grep, and we get false negative build results. Ideally our logfile shouldn't contain uppercase FAIL for expected failures. In the past, the usual keyword for detecting a failure was FAILED. I wonder if I had changed that to FAIL because of gtests. I'm not sure. However, just yesterday we changed the gtest to print html_passed or html_failed lines for each individual gtest, which means, we'll a get PASSED or FAILED for each gtest, too. So, I suggest we change the grep to search for "FAILED".
Assignee | ||
Comment 1•8 years ago
|
||
Attachment #8778344 -
Flags: review?(ttaubert)
Assignee | ||
Updated•8 years ago
|
Attachment #8778344 -
Flags: review?(ekr)
Comment 2•8 years ago
|
||
Comment on attachment 8778344 [details] [diff] [review] 1292611-v1.patch Review of attachment 8778344 [details] [diff] [review]: ----------------------------------------------------------------- The whole approach seems brittle, but so is having multiple test suites with different output formats :| I'm fine with this if it fixes gtests false-negatives on buildbot.
Attachment #8778344 -
Flags: review?(ttaubert) → review+
Assignee | ||
Comment 3•8 years ago
|
||
https://hg.mozilla.org/projects/nss/rev/1299323cf18b
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.27
Assignee | ||
Comment 4•8 years ago
|
||
(In reply to Tim Taubert [:ttaubert] from comment #2) > I'm fine with this if it fixes gtests false-negatives on buildbot. It fixed it.
Comment 5•8 years ago
|
||
(In reply to Kai Engert (:kaie) from comment #4) > (In reply to Tim Taubert [:ttaubert] from comment #2) > > I'm fine with this if it fixes gtests false-negatives on buildbot. > > It fixed it. \o/
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → kaie
You need to log in
before you can comment on or make changes to this bug.
Description
•